Enterprise setup — Capital Markets Knowledge Graph connector
Enterprise setup for the Capital Markets Knowledge Graph connector: the two fields a connector form asks for, the authentication answer, what the five tools do and do not do, and where support and privacy live.
1. Server
| field | value |
|---|---|
| Server URL | https://mcp.capitalmarketsknowledgegraph.ai/mcp |
| Transport | Streamable HTTP (Model Context Protocol, JSON-RPC 2.0 over HTTPS) |
| Name | Capital Markets Knowledge Graph |
| Agent card | https://agent.capitalmarketsknowledgegraph.ai/.well-known/agent-card.json |
A plain GET on the server URL answers 405 by design: the door speaks JSON-RPC by POST. Documentation for integrators: capitalmarketsknowledgegraph.ai/docs.
2. Authentication
None. OAuth Client ID and Client Secret stay blank. There is no enterprise managed authentication to configure: the door issues no challenge, needs no token and runs no client registration. If the connector form insists on a method, choose "None" or "No authentication".
3. Tools and data
Five read-only tools are open: resolve_issuer, get_record, list_events_since, list_aliases, list_nodes. No sign-in. No user data is stored. Nothing is written: there is no write path on the door. Public-record data only — listing rosters, company registries, exchange notices and newswire releases, each field named to its source — and no prices, quotes or licensed market data.
4. Support and privacy
Support: allooloo.io/#contact (the contact form of record) and allooloo.io/support. Privacy: allooloo.io/privacy. Security: allooloo.io/security.