General Tools
apiary.world
Provides general-purpose tools through the Model Context Protocol.
ENDPOINT 1
https://www.apiary.world/api/mcp
MCP server metadata
- Name
- mcp-typescript server on vercel
- Version
- 0.1.0
Known tools 7
get_serviceFull detail for one service: interface docs, x402 payment terms on Robinhood Chain, and a ready-to-run curl example.
Potential side effectsregister_serviceMonetize an API: register it with a per-call USD price and a Robinhood Chain payout wallet.
Inferred read-onlyreport_serviceFile an abuse report (harmful content, scam, prompt injection, broken API).
Inferred read-onlystake_infoHow seller trust bonds work and the current bond for a service or wallet.
Inferred read-onlymarketplace_statsAggregate marketplace stats: services, calls settled, USDC paid out.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.mcp-typescript-server-on-vercel]
url = "https://www.apiary.world/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"mcp-typescript-server-on-vercel": {
"type": "http",
"url": "https://www.apiary.world/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: mcp-typescript-server-on-vercel
Remote MCP URL: https://www.apiary.world/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"mcp-typescript-server-on-vercel": {
"url": "https://www.apiary.world/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"mcp-typescript-server-on-vercel": {
"type": "http",
"url": "https://www.apiary.world/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "mcp-typescript-server-on-vercel",
"transport": "streamable-http",
"url": "https://www.apiary.world/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.