StitchAPI MCP server

• Registry namedev.stitchapi/docsverified in the MCP registry

The registry name sits under stitchapi.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-24
• Tools2
• Server calls itselfstitchapi-docs
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 124 ms.

• Its tools do none of the product's use cases we checked: Call an external REST endpoint as a typed, validated function; Expose an external API to an AI agent as a tool; Stream LLM responses back to an app token by token.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score65 of 100answers 100 · does the job 0 · definitions 83 · context 100 · use 39 · connects 100
• What an agent can do with it0 of 3 use cases
• Use88 npm downloads a week21 GitHub stars
• Answered100% of days10 of 10 daily checks
• Median first answer199 ms
• Space in an agent's context≈ 273 tokensthe definitions of all its tools (2), which an agent carries on every turn
• Tool definitionsB · 83 of 100
• Typed results0 of 2 toolsdeclared outputSchema: results come typed, read once

• Not saying whether it only reads or can destroy: 2 of 2

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• search_docs

  Search the StitchAPI documentation semantically (hybrid BM25 + vector). Returns the most relevant doc sections as excerpts with deep links — never full pages. Follow up with get_doc to read a full page.

• get_doc

  Fetch a full StitchAPI documentation page as Markdown — the "read the whole thing" escape hatch for a search_docs hit. Pass a `url` (as returned by search_docs) or a `slug` like "guides/resilience/throttle".