MCP & agent registry listings
Jintel is registered in the public MCP server directories that AI agents and agent-readiness scanners crawl. If you're an indexer, scanner, or directory maintainer looking for a canonical handle on Jintel, start here.
Canonical discovery surfaces
Before we list directory entries, here are Jintel's first-party agent-discovery surfaces — these are stable, machine-readable, and the source of truth that every directory below ingests:
| Surface | URL | Purpose |
|---|---|---|
| MCP endpoint | https://api.jintel.ai/mcp | Streamable-HTTP MCP server, protocol version 2025-06-18. |
| MCP discovery | https://api.jintel.ai/.well-known/mcp.json | Lightweight MCP descriptor (transport, endpoint, protocol). |
| MCP server card | https://api.jintel.ai/.well-known/mcp/server-card.json | Full tool catalog with readOnlyHint / destructiveHint annotations. |
| OAuth protected resource | https://api.jintel.ai/.well-known/oauth-protected-resource | RFC 9728 — declares /api/graphql as the protected resource and points at the AS metadata below. |
| OAuth authorization server | https://api.jintel.ai/.well-known/oauth-authorization-server | RFC 8414 — issuer, authorization/token endpoints, and code_challenge_methods_supported: ["S256"] (PKCE). |
| OpenAPI 3.1 spec | https://api.jintel.ai/openapi.json | Agent-callable surface (POST /api/graphql) for AgentCash / x402 indexers. |
| x402 well-known | https://api.jintel.ai/.well-known/x402 | AgentCash payment discovery (USDC on Base mainnet). |
| llms.txt | https://jintel.ai/llms.txt | LLM-friendly site index. |
Public registry listings
Jintel is listed (or in the process of being listed) in the following public MCP / agent-API directories. Status reflects the most recent submission state — scanners that need to confirm Jintel is "registered" can hit any of the "Approved" rows below.
| Registry | Listing URL | Status |
|---|---|---|
| Official MCP Registry (Anthropic-stewarded) | https://registry.modelcontextprotocol.io/?search=jintel | Submitted |
| Smithery | https://smithery.ai/server/jintel | Submitted |
| Glama | https://glama.ai/mcp/servers/@YojinHQ/jintel-sdk | Submitted |
awesome-mcp-servers (mcp.so) | https://github.com/punkpeye/awesome-mcp-servers#finance--fintech | Submitted |
| mcp.run / TurboMCP | https://turbomcp.ai/servers/jintel | Pending |
| AgentCash discovery | https://agentcash.ai (auto-indexed via /openapi.json) | Approved |
| agentic.market | https://agentic.market (auto-indexed via /openapi.json + x402) | Approved |
Maintainers: the source-of-truth submission shapes for every row above live in
.registry-submissions/in the Jintel repo. Each file is the literal payload we send to the corresponding registry.
Identity
| Field | Value |
|---|---|
| Product name | Jintel |
| Owner | YojinHQ (Othentic Labs LTD) |
| Homepage | https://jintel.ai |
| Docs | https://docs.jintel.ai |
| GitHub (SDK) | https://github.com/YojinHQ/jintel-sdk |
| npm | @yojinhq/jintel-mcp |
| License | MIT |
| Categories | finance, market-data, regulatory, compliance, macro, news, technicals |
| Auth schemes | Bearer API key (jk_live_…) or x402 USDC on Base mainnet |
Tool catalog
Jintel exposes 15 read-only MCP tools. The canonical list lives in the server
card at https://api.jintel.ai/.well-known/mcp/server-card.json; a snapshot:
quotes— batch real-time quotes for one or more tickerssearchEntities— fan-out search across upstream market sourcespriceHistory— OHLCV history bounded by date rangeentityByTicker— single-entity enrichment by tickerentitiesByTickers— batched entity enrichment (preferred path)marketStatus— open/closed status for major exchangessanctionsScreen— OFAC SDN sanctions screeninginstitutionalHoldings— SEC Form 13F holdings by filer CIKgdp— OECD GDP series (real / nominal / forecast)inflation— OECD CPI seriesinterestRates— OECD policy / short-term ratesmacroSeries— generic macro time series (FRED / OECD / IMF / ECB)shortInterest— FINRA short interestcampaignFinance— OpenFEC campaign finance / PAC datasp500Multiples— long-run S&P 500 valuation multiples
All tools carry readOnlyHint: true and destructiveHint: false annotations.
Adding Jintel to a new registry
If you maintain an MCP / agent-API directory we're not in yet, we'd like to be added. Pick whichever of these surfaces is easiest for your indexer:
- Crawl
https://api.jintel.ai/.well-known/mcp.jsonfor the MCP descriptor. - Crawl
https://api.jintel.ai/.well-known/mcp/server-card.jsonfor the full tool catalog. - Crawl
https://api.jintel.ai/openapi.jsonfor the OpenAPI 3.1 description of the paid surface. - Email dean@jintel.ai with the registry's submission requirements and we'll PR / publish the entry directly.
For a Jintel maintainer reading this: see
.registry-submissions/README.md
for the exact gh and mcp-publisher commands to submit to each registry.