Manufact
Product▾
- MCP HostingDeploy MCP apps and servers to production.
- Cross-client testingRun the same checks across ChatGPT, Claude, and more.
- Publishing checksAudit your MCP app against ChatGPT Apps Store and Cloud Connectors requirements.
- Submission PackGenerate the assets you need for marketplace submission.
- Cloud InspectorTrace, replay, and debug MCP traffic in production.
- Public chatEmbeddable chat surfaces for your product.
- AnalyticsUsage, latency, and reliability in one place.
- Products
- Cloud
- mcp-use SDK
- Inspector
- Vibe
Developers▾
- Manufact docsBuild, deploy, and operate on Manufact Cloud.
- SupportCommunity, issue reporting, and premium support.
- TemplatesStart from a deploy-ready MCP framework template.
- mcp-use docsBuild MCP apps and servers with the mcp-use SDK.
- mcp-use Inspector DocsInspect and debug MCP servers from your browser.
- mcp-use client CLIConnect to and call MCP servers from your terminal.
- MCP server tunnelingExpose a local MCP server through a secure tunnel.
- Pricing
- Blog
Sinch Build Docs
developers.sinch.com/mcp
Good
Protocol
Tools
All tools have descriptions
All tools have non-empty descriptions
All tools have OpenAI behavior hints
4 behavior annotation issue(s) found
How to fix: On each tool, declare annotations.readOnlyHint, annotations.destructiveHint, and annotations.openWorldHint as booleans. The policy review separately assesses whether their values match the tool's actual behavior.
Tool input schemas have a valid object structure
All tool input schemas have a valid object structure
Tool names use valid characters
All tool names use valid characters
Tool names follow the MCP 1–128 character range
All tool names follow the MCP recommended length
Tool names follow MCP uniqueness guidance
All tool names are unique
Tool input header annotations are valid
All x-mcp-header annotations satisfy Streamable HTTP requirements
Declared output schemas have a valid basic structure
0 declared output schema(s) pass basic structural validation; schemas may describe any JSON value, including arrays
Tool-linked resource URI is readable
No view resources found — view checks skipped
Tool text has no hidden control characters
No invisible or control characters found in tool-facing text
Tool visibility metadata is valid
No view resources found — view checks skipped
Tool invocation metadata present
No view resources found — view checks skipped
MCP Apps
View resource metadata complete
No view resources found — view checks skipped
All discovered view resources were inspected
No view resources found — view checks skipped
CSP metadata covers literal external origins
No view resources found — view checks skipped
View resource envelope is valid
No view resources found — view checks skipped
View resources declare a domain
No view resources found — view checks skipped
Declared domains respond
No view resources found — view checks skipped
Client compatibility
Skills over MCP resources are readable
Server does not advertise the Skills over MCP extension
Claude Code metadata fits its 2 KB fields
Tool descriptions and server instructions fit Claude Code's 2 KB fields
Claude tool names are within 64 characters
All tool names are within Claude's 64-character limit
Claude tools declare applicable behavior hints
1 Claude behavior annotation issue(s) found
How to fix: For Claude directory submission, declare the applicable annotations.readOnlyHint or annotations.destructiveHint value as a boolean on every tool.
Cursor tool-name budget advisory
No tool name independently exhausts Cursor's observed 60-character combined budget
ChatGPT tool names are unique
All tool names are unique
All tools have a display title
1 tool(s) missing a display title: describe-tools
How to fix: Set the top-level tool.title to a short human-readable label (for example, "Search catalog"). Claude directory submission requires tool titles; annotations.title remains accepted only as a legacy fallback.
OpenAI file parameters use valid schemas
All declared OpenAI file parameters use reviewer-valid schemas
Overview
- Author
- Sinch
- Verification
- community
- Auth
- None — public endpoint
- Categories
- developer-tools
- Works with
- claudeclaude-apiclaude-codeclaude-desktop
- Docs
- Documentation
get-endpoint-infoget-endpointsget-full-api-descriptionget-security-schemeslist-apissearchRelated MCP servers
FAQ
Sinch Build Docs install, tools, readiness, and alternatives.
How do I add Sinch Build Docs to Claude, ChatGPT, or Cursor?
Add Sinch Build Docs to Claude, ChatGPT, or Cursor by connecting its remote MCP URL in each client's MCP settings. In Claude, add a custom connector. In ChatGPT, add an MCP app. In Cursor, add an MCP server under Settings. The MCP URL is https://developers.sinch.com/mcp.
Is Sinch Build Docs MCP ready for ChatGPT and Claude?
As of September 15, 2026, Sinch Build Docs scores 82/100 on Manufact's MCP publishing checklist. The scan does not yet meet ChatGPT publishing checks and does not yet meet Claude publishing checks.
What tools does the Sinch Build Docs MCP server provide?
Sinch Build Docs provides these MCP tools: get-endpoint-info, get-endpoints, get-full-api-description, get-security-schemes, list-apis, and search.
What are the best alternatives to Sinch Build Docs?
As of September 16, 2026, alternatives to Sinch Build Docs in developer-tools on the Manufact MCP catalog include ADITUS Developer Portal MCP, Credits.fm, Ezoic Setup, Keenable Web Search, and Keyword Tool: Free SEO Keyword Research.
Does Sinch Build Docs MCP require authentication?
Sinch Build Docs does not require authentication. It is a public MCP endpoint you can connect without logging in.
Who develops Sinch Build Docs?
Sinch Build Docs is developed by Sinch. It is listed as community on the Claude connector directory.
Not your MCP?
Scan any public or OAuth MCP URL against ChatGPT and Claude publishing checks. No account required.