Vendor: smithery.ai · entry id 07-smithery · source 07-mcp-infrastructure.md line 96
An MCP server is not a meaningful question for this entry. The status was established on 2026-08-24 and has not been re-fetched since.
mcp_status, verbatim from the file:
n/a (Smithery is the registry itself, not a vendor's own product MCP)
mcp_url, verbatim from the file:
https://smithery.ai
api_gate, verbatim from the file:
free to browse; some individual listed servers charge per-call (e.g. one listed server at $0.01-$0.05/call) while others are free/open-source - pricing is per-server, not a single Smithery tier.
No documentation URL recorded.
263 of 293 entries are in the same position. Blank is legal and it is published as blank.
Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.
The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.
A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.
Tagged by machine-pass on 2026-08-25 against the closed 55 job vocabulary. 271 of 293 entries carry at least one tag; 827 tags are assigned in total.
1 source URL. Thin. The standing rule is at least two independent sources with the vendor's own site unable to be both of them, and this entry does not meet it. 32 entries are in the same state and they are listed on the methodology page. Raw sources field, verbatim:
https://smithery.ai
Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.