Devuelve la especificación OpenAPI 3.1 de la API pública de Ghosty Studio (YAML).
ConnectorNo auth
726,946 tools. Updated 2026-10-31 01:22
"openapi" matching MCP tools:
- Checks an OpenAPI 3.0/3.1 document (as JSON): version, info, paths, responses, unique operationIds, declared path parameters and unresolved local $refs. Returns { valid, version, operations, refs, unresolvedRefs, errors: [{ path, message }], warnings: [{ path, message }] } Price: 2 credits (1 credit = 1 CAD cent) per successful call; input that does not match the schema is rejected before billing.ConnectorNo auth
- OpenAPI version key shape, body discardedConnectorNo auth
- Get an OpenAPI 3.0 specification for a BANKSapi API, or a targeted slice of one. Available specs: banks-connect (main API), ai-connect (AI features), pay-connect (payments). Pass operation_id to get just that operation with the schemas it references (strongly preferred — the full specs are large). Pass tag to get every operation of one section. With neither, returns the entire spec. To discover operationIds and tags, fetch the API index via get-banksapi-docs-page('/api/<spec_name>'). Returns YAML for YAML specs, JSON for JSON specs.ConnectorNo auth
- Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Mintlify documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks. This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its `.mdx` path to `head` or `cat` — a page at the URL path `/some/page` lives at `/some/page.mdx`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`. **Paths are specific to this site — never guess them.** Discover real paths with `tree / -L 2`, `ls /`, or the search tool before reading. If a path does not exist, that only means the guess was wrong; it does NOT mean the topic is undocumented — use `rg -il "keyword" /` to find where it is covered. **Workflow:** Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path. Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage. Each call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /some-directory && ls` or `ls /some-directory`). Do NOT assume that `cd` in one call affects the next call. Examples (replace the placeholder paths with real ones from `tree` or search): - `tree / -L 2` — see the top-level directory layout - `rg -il "rate limit" /` — find all files mentioning "rate limit" - `rg -C 3 "apiKey" /some-directory/` — show matches with 3 lines of context around each hit - `head -80 /some/page.mdx` — read the top 80 lines of a specific page - `head -80 /page-one.mdx /page-two.mdx /section/page-three.mdx` — read multiple pages in one call - `cat /some/page.mdx` — read a full page when you need everything - `cat /openapi/zh/static-export-openapi.json | jq '.paths | keys'` — list OpenAPI endpoints OpenAPI specs for this site are mounted at: `/openapi/zh/static-export-openapi.json`, `/openapi/zh/openapi.json`, `/openapi/zh/discovery-openapi.json`, `/openapi/zh/analytics.openapi.json`, `/openapi/zh/admin-openapi.json`, `/openapi/fr/static-export-openapi.json`, `/openapi/fr/openapi.json`, `/openapi/fr/discovery-openapi.json`, `/openapi/fr/analytics.openapi.json`, `/openapi/fr/admin-openapi.json`, `/openapi/es/static-export-openapi.json`, `/openapi/es/openapi.json`, `/openapi/es/discovery-openapi.json`, `/openapi/es/analytics.openapi.json`, `/openapi/es/admin-openapi.json`, `/openapi/static-export-openapi.json`, `/openapi/openapi.json`, `/openapi/discovery-openapi.json`, `/openapi/analytics.openapi.json`, `/openapi/admin-openapi.json`. Use them to answer questions about endpoints, request/response schemas, parameters, and authentication. Output is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 "pattern" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible. When referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/some/page.mdx` becomes `/some/page`.ConnectorNo auth
- Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Sorsa Developer Platform documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks. This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its `.mdx` path to `head` or `cat` — a page at the URL path `/some/page` lives at `/some/page.mdx`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`. **Paths are specific to this site — never guess them.** Discover real paths with `tree / -L 2`, `ls /`, or the search tool before reading. If a path does not exist, that only means the guess was wrong; it does NOT mean the topic is undocumented — use `rg -il "keyword" /` to find where it is covered. **Workflow:** Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path. Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage. Each call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /some-directory && ls` or `ls /some-directory`). Do NOT assume that `cd` in one call affects the next call. Examples (replace the placeholder paths with real ones from `tree` or search): - `tree / -L 2` — see the top-level directory layout - `rg -il "rate limit" /` — find all files mentioning "rate limit" - `rg -C 3 "apiKey" /some-directory/` — show matches with 3 lines of context around each hit - `head -80 /some/page.mdx` — read the top 80 lines of a specific page - `head -80 /page-one.mdx /page-two.mdx /section/page-three.mdx` — read multiple pages in one call - `cat /some/page.mdx` — read a full page when you need everything - `cat '/openapi/https://api.sorsa.io/v3/swagger.json' | jq '.paths | keys'` — list OpenAPI endpoints OpenAPI specs for this site are mounted at: `'/openapi/https://api.sorsa.io/v3/swagger.json'`, `/openapi/openapi-pt-BR.json`, `/openapi/openapi-es.json`, `/openapi/openapi-zh-Hans.json`, `/openapi/openapi-ja.json`, `'/openapi/document(1).json'`, `/openapi/v3/openapi.json`, `/openapi/v2/openapi.json`. Use them to answer questions about endpoints, request/response schemas, parameters, and authentication. Output is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 "pattern" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible. When referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/some/page.mdx` becomes `/some/page`.ConnectorNo auth
Matching MCP Servers
- AlicenseNot gradedqualityDmaintenanceThis tool creates a Model Context Protocol (MCP) server that acts as a proxy for any API that has an OpenAPI v3.1 specification. This allows you to use Claude Desktop to easily interact with both local and remote server APIs.937 npm905MIT
- AlicenseAqualityBmaintenanceTurns an existing Express, Hono, Fastify, or Next.js API into a Streamable HTTP MCP endpoint, exposing one tool per OpenAPI operation that runs in-process through the app's existing routes, auth, validation, and handlers. It also serves discovery documents and readiness guidance so models can better understand and call the API.3MIT
Matching MCP Connectors
Official Openapi® MCP server: Italian company data, PEC, SMS, vehicles, geocoding and more APIs.
MCP server (stdio): lint OpenAPI specs with Spectral via the AgentForge API
- Returns operationIds, HTTP methods, paths, and query parameter names from the bundled OpenAPI spec (no network). Use before t54_x402_request or per-SKU tools.ConnectorNo auth
- Tier-0 front door for the current session page (or pass url): does the site offer an agent-native interface (llms.txt / OpenAPI / ai-plugin)? Prefer it over scraping.ConnectorNo auth
- Check live API & system health — operational/degraded verdict, per-source freshness, MCP tool count — Public health status of all CryptoWhaleInsights data sources, MCP server, and OpenAPI spec. Returns overall verdict (operational/degraded/outage), per-source health with age in seconds, recent 24-hour error count, MCP tool count, and OpenAPI path count. Useful for AI agents and developers to verify the platform is live before making requests. Cached ~30s.ConnectorNo auth
- Produce a full changelog of every detected change between two OpenAPI specifications (base vs revision), down to informational changes. Pass both specs as YAML or JSON. Use this when you want the complete set of changes at every severity. Use oasdiff_breaking_changes instead when you only care whether the change is breaking (less noise), or oasdiff_diff for the raw structural diff without a backward-compatibility judgment. Both specs must be valid, self-contained OpenAPI (external $ref URLs or files are not resolved).ConnectorNo auth
- Show the structural diff between two OpenAPI specifications (base vs revision): what was added, removed, or modified. Pass both specs as YAML or JSON. Use this when you want the raw structural changes rather than a backward-compatibility verdict. Use oasdiff_breaking_changes to judge whether changes break clients, or oasdiff_changelog for a severity-classified changelog. Both specs must be valid, self-contained OpenAPI (external $ref URLs or files are not resolved).ConnectorNo auth
- Read an OpenAPI 3 or Swagger 2 document (JSON or YAML, up to 2 MB) from a URL and summarise it for an agent: title, version, description, servers, auth schemes, operation count by method, tags, which operations are paid (402 or x-payment-info) or deprecated, and up to 150 operations with method, path, summary and operationId. Use before calling an unfamiliar API, to pick an endpoint, or to compare APIs. Example: url=https://petstore3.swagger.io/api/v3/openapi.json. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.ConnectorNo auth
- Read an OpenAPI 3 or Swagger 2 document (JSON or YAML, up to 2 MB) from a URL and summarise it for an agent: title, version, description, servers, auth schemes, operation count by method, tags, which operations are paid (402 or x-payment-info) or deprecated, and up to 150 operations with method, path, summary and operationId. Use before calling an unfamiliar API, to pick an endpoint, or to compare APIs. Example: url=https://petstore3.swagger.io/api/v3/openapi.json. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.ConnectorNo auth
- Read an OpenAPI 3 or Swagger 2 document (JSON or YAML, up to 2 MB) from a URL and summarise it for an agent: title, version, description, servers, auth schemes, operation count by method, tags, which operations are paid (402 or x-payment-info) or deprecated, and up to 150 operations with method, path, summary and operationId. Use before calling an unfamiliar API, to pick an endpoint, or to compare APIs. Example: url=https://petstore3.swagger.io/api/v3/openapi.json. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.ConnectorNo auth
- Get metadata about erikbethke.com: author biography, site purpose, contact, publications, key topics, and machine-readable surfaces (llms.txt, agents.json, MCP, OpenAPI).ConnectorNo auth
- Get the full agentic readiness report for a specific domain: score, category, all 7 signal checks (llms.txt, ai-plugin.json, OpenAPI, structured API, MCP server, robots.txt AI rules, Schema.org), plus any cached llms.txt content and OpenAPI summary. When an exact search_id newly records this organic-result selection, the response also carries an optional record_action_interest opportunity for this domain. Selection alone is never interest and never contacts the provider.ConnectorNo auth
- Every artifact a provider publishes — provider-level (MCP, security, scopes, rules, agentic-access) and per-API (OpenAPI, Arazzo, overlays, reference docs) — grouped by type with counts. by_type_counts is the full summary; pass `type` (e.g. OpenAPI, MCP) to scope the artifacts list to one type, since an unfiltered provider can be 250+ entries.ConnectorNo auth
- Get the full OpenAPI definition for a single operation by operationId (method, path, parameters, request body, responses). Use adn_list_operations to find operationIds.ConnectorNo auth
- Return the canonical endpoint, OpenAPI, 17 required fields and a locally fillable MS-DEC-250 template. It accepts no buyer data and never creates an order.ConnectorNo auth
- Return the canonical endpoint, OpenAPI, 17 required fields and a locally fillable MS-DEC-250 template. It accepts no buyer data and never creates an order.ConnectorNo auth
- [FREE] List all AgentWorld Data API endpoints with prices and the OpenAPI spec URL. Use this to discover the full paid dataset query catalog.ConnectorNo auth