このMCPでできること
Acts as a gateway between LLM agents and external data through multiple tools and an endpoint catalog.
機能
ツール
11
ツール
call_endpoint
Call a Sugra API endpoint by operation_id from the bundled catalog.
Plan calls with describe_endpoint's agent_hints: duration_class "fast"
usually responds in under ~2s, "slow" usually 1-5s and occasionally 15s+
on a cold upstream, "heavy" can exceed the gateway timeout - keep parallel
calls within max_concurrency and prefer small batches. Bulk endpoints bill
1 request credit per body item. Failures return structured errors {error,
reason, status_code, elapsed_ms, retry_hint}; after "upstream_timeout" a
single retry often succeeds because the aborted attempt warms upstream
caches.
読み取り専用
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', 'title': 'call_endpointArguments', 'required': ['operation_id'], 'properties': {'body': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'array', 'items': {'type': 'object', 'additionalProperties': True}}, {'type': 'null'}], 'title': 'Body', 'default': None, 'description': "JSON request body for a POST operation, matching the request_body_schema returned by describe_endpoint(operation_id): a JSON object for most operations, or a JSON array when that schema's top-level type is array. Omit for GET operations."}, 'limit': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Limit', 'default': None, 'description': 'Bounds ONLY the records list: the data list, a bare top-level array, or the list inside an object data when exactly one of these keys holds a list: data, entries, events, history, items, observations, points, records, results, rows, series, timeseries (for example data.items). When data has no such single list but every one of its values is an object holding exactly one list named observations, limit bounds each data.<key>.observations list on its own (records_path data.*.observations); fields there still names keys of data. Otherwise, no such list, or several, means the limit does not apply. Keys beside the list such as total and count are not rewritten, and lists nested inside records are never truncated. limit keeps the newest N records when every record carries one date or period key in one format and the list runs one way by it, else the first N, and meta.shaped reports limit_applied, records_path and, for a bounded records list, order (asc, desc or unknown) and kept_end (newest or first), as maps by name for sibling sub-series.'}, 'fields': {'anyOf': [{'type': 'array', 'items': {'type': 'string'}}, {'type': 'null'}], 'title': 'Fields', 'default': None, 'description': 'Optional projection of keys to keep on each record of the records list: the data list, a bare top-level array, or the list inside an object data when exactly one of these keys holds a list: data, entries, events, history, items, observations, points, records, results, rows, series, timeseries (for example data.items). Keys beside that list such as total and count stay. If a field names a key of data itself, or of a payload without data, that object is projected instead; an object data without such a list is otherwise kept whole. Dotted paths (geo.city) walk nested objects. If no field matches, nothing is removed. meta.shaped reports fields_applied, fields_unmatched and records_path. Omit to keep every key.'}, 'params': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}], 'title': 'Params', 'default': None, 'description': 'Query and path parameters for this operation_id. Keys and types are operation-specific - call describe_endpoint(operation_id) first to get the exact parameter names, types, and examples. Omit if the operation takes none. A key the operation does not declare returns error unknown_parameters with the accepted names and did_you_mean, before any request is made.'}, 'include_raw': {'type': 'boolean', 'title': 'Include Raw', 'default': False, 'description': 'If true, attach the original unshaped payload under raw when it fits the size cap; otherwise meta.raw_omitted explains why. Default false.'}, 'operation_id': {'type': 'string', 'title': 'Operation Id'}}}
出力スキーマ
{'type': 'object', 'title': 'call_endpointDictOutput', 'additionalProperties': True}
describe_endpoint
Describe one Sugra API endpoint by operation_id.
Includes agent_hints (duration_class fast/slow/heavy, max_concurrency,
bulk billing) so you can budget timeouts and parallelism before calling.
POST endpoints with a JSON body also carry request_body_schema (the
resolved JSON schema) - construct the `body` argument from it instead
of guessing key names. Call this after search_endpoints and before
call_endpoint when you need the exact parameter names and examples.
読み取り専用
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', 'title': 'describe_endpointArguments', 'required': ['operation_id'], 'properties': {'operation_id': {'type': 'string', 'title': 'Operation Id', 'description': 'Catalog operation_id from search_endpoints (or from list_toolsets drill-down). Unknown ids return error unknown_operation_id.'}}}
出力スキーマ
{'type': 'object', 'title': 'describe_endpointDictOutput', 'additionalProperties': True}
fetch_data
One-step fetch: find the best Sugra endpoint for the query and call it.
Combines search_endpoints + call_endpoint into a single round trip. Use
this when you want data without manually picking an operation_id. The
full search_endpoints + describe_endpoint + call_endpoint dance is still
available when you need explicit control, but for most natural-language
queries this tool is enough.
Behavior:
1. Search the bundled catalog for the query. Top match wins.
2. If the matched endpoint has required parameters and they are all
provided in `params`, call it and return the response.
3. If required parameters are missing, return the candidate endpoints
and the missing-params list so the LLM can retry with the correct
`params` dict on the next call.
Examples:
- `fetch_data("US CPI inflation", params={"series_id": "CPIAUCSL"})`
â calls /api/v1/fred/series/CPIAUCSL, returns observations.
- `fetch_data("Bitcoin price", params={"coin_id": "bitcoin"})`
â calls /api/v1/crypto/bitcoin/price.
- `fetch_data("Latest financial news")`
â news_latest has no required params, returns latest news directly.
読み取り専用
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', 'title': 'fetch_dataArguments', 'required': ['query'], 'properties': {'body': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'array', 'items': {'type': 'object', 'additionalProperties': True}}, {'type': 'null'}], 'title': 'Body', 'default': None, 'description': "JSON body for an auto-selected POST operation; the tool returns the request_body_schema to fill when the match needs one. Pass a JSON object or a JSON array as that schema's top-level type dictates."}, 'limit': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Limit', 'default': None, 'description': 'Bounds ONLY the records list: the data list, a bare top-level array, or the list inside an object data when exactly one of these keys holds a list: data, entries, events, history, items, observations, points, records, results, rows, series, timeseries (for example data.items). When data has no such single list but every one of its values is an object holding exactly one list named observations, limit bounds each data.<key>.observations list on its own (records_path data.*.observations); fields there still names keys of data. Otherwise, no such list, or several, means the limit does not apply. Keys beside the list such as total and count are not rewritten, and lists nested inside records are never truncated. limit keeps the newest N records when every record carries one date or period key in one format and the list runs one way by it, else the first N, and meta.shaped reports limit_applied, records_path and, for a bounded records list, order (asc, desc or unknown) and kept_end (newest or first), as maps by name for sibling sub-series.'}, 'query': {'type': 'string', 'title': 'Query', 'description': "Natural-language request for data (examples: 'US CPI', 'Bitcoin price', 'latest news'). The tool picks the top catalog match and calls it. If required params are missing it returns needs_params instead of guessing."}, 'fields': {'anyOf': [{'type': 'array', 'items': {'type': 'string'}}, {'type': 'null'}], 'title': 'Fields', 'default': None, 'description': 'Optional projection of keys to keep on each record of the records list: the data list, a bare top-level array, or the list inside an object data when exactly one of these keys holds a list: data, entries, events, history, items, observations, points, records, results, rows, series, timeseries (for example data.items). Keys beside that list such as total and count stay. If a field names a key of data itself, or of a payload without data, that object is projected instead; an object data without such a list is otherwise kept whole. Dotted paths (geo.city) walk nested objects. If no field matches, nothing is removed. meta.shaped reports fields_applied, fields_unmatched and records_path. Omit to keep every key.'}, 'params': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}], 'title': 'Params', 'default': None, 'description': "Parameters for the auto-selected endpoint. If omitted and the best-match endpoint has required parameters, the tool returns that endpoint's required_parameters and examples so you can retry with them filled in."}, 'include_raw': {'type': 'boolean', 'title': 'Include Raw', 'default': False, 'description': 'If true, attach the original unshaped payload under raw when it fits the size cap; otherwise meta.raw_omitted explains why. Default false.'}}}
出力スキーマ
{'type': 'object', 'title': 'fetch_dataDictOutput', 'additionalProperties': True}
get_snapshot
Composed current view of an entity via a named recipe.
Executes a fixed server-side recipe (company_snapshot, etf_snapshot,
quote_snapshot, macro_indicator_snapshot, macro_calendar,
earnings_snapshot, debt_snapshot) and returns one envelope with freshness,
provenance, per-component coverage, and billing. Composed calls charge the
recipe's fixed cost (1-2 units) from the daily quota. status "partial"
means an optional component was unavailable - the present components are
still trustworthy; honor the freshness block (stale=true means the data
aged past its budget); for macro_calendar, entity is accepted but does
not filter the calendar.
Args:
recipe: Recipe name from the fixed manifest.
entity: Entity dict from resolve_entity ({"namespace": ..., "ids": ...}).
読み取り専用
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', 'title': 'get_snapshotArguments', 'required': ['recipe', 'entity'], 'properties': {'entity': {'type': 'object', 'required': ['namespace', 'ids'], 'properties': {'ids': {'type': 'object', 'description': 'Identifier map from resolve_entity.', 'additionalProperties': True}, 'namespace': {'type': 'string', 'description': 'Entity namespace from resolve_entity.'}}, 'description': 'Entity dict from resolve_entity ({namespace, ids}). Extra keys are ignored.', 'additionalProperties': True}, 'recipe': {'type': 'string', 'title': 'Recipe'}}}
出力スキーマ
{'type': 'object', 'title': 'get_snapshotDictOutput', 'additionalProperties': True}
get_timeseries
Bounded timeseries for an entity: price, macro_series, etf_flows or
etf_monthly_flows.
Returns points oldest-first with an explicit downsampling flag when the
raw series exceeded max_points. Times are UTC. Costs 1 unit per call.
The two ETF flow metrics answer different questions and are not
interchangeable. ``etf_flows`` is an ESTIMATE at filing cadence: one point
per SEC filing refresh, so ``t`` is a filing date and even a wide window
yields a handful of points. ``etf_monthly_flows`` is the fund's own
creations and redemptions from its NPORT-P filing, so ``t`` is a calendar
month (``YYYY-MM``) and each point carries the three filed components -
sales, reinvestment, redemption - beside the net.
Two things to read before quoting etf_monthly_flows. NPORT-P is filed per
SERIES, so for a fund with more than one share class the figures cover
every class and the payload says so in ``multi_class_series``; where the
class count is unknown it says ``class_scope`` instead of staying silent.
And a fund that files no NPORT-P at all, such as a commodity trust, is not
an error: the call returns status ``partial`` with an empty point list and
a ``reason``.
Args:
metric: One of price / macro_series / etf_flows / etf_monthly_flows.
entity: Entity dict from resolve_entity ({"namespace": ..., "ids": ...}).
granularity: Requested point granularity (default "1d").
max_points: Hard cap on returned points (default 500).
読み取り専用
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', 'title': 'get_timeseriesArguments', 'required': ['metric', 'entity'], 'properties': {'entity': {'type': 'object', 'required': ['namespace', 'ids'], 'properties': {'ids': {'type': 'object', 'description': 'Identifier map from resolve_entity.', 'additionalProperties': True}, 'namespace': {'type': 'string', 'description': 'Entity namespace from resolve_entity.'}}, 'description': 'Entity dict from resolve_entity ({namespace, ids}). Extra keys are ignored.', 'additionalProperties': True}, 'metric': {'enum': ['price', 'macro_series', 'etf_flows', 'etf_monthly_flows'], 'type': 'string', 'title': 'Metric'}, 'max_points': {'type': 'integer', 'title': 'Max Points', 'default': 500}, 'granularity': {'type': 'string', 'title': 'Granularity', 'default': '1d'}}}
出力スキーマ
{'type': 'object', 'title': 'get_timeseriesDictOutput', 'additionalProperties': True}
list_sources
List source families in the bundled catalog with endpoint counts.
Use the family names as the source filter on search_endpoints. This
does not call the Sugra API.
読み取り専用
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', 'title': 'list_sourcesArguments', 'properties': {}}
出力スキーマ
{'type': 'object', 'title': 'list_sourcesDictOutput', 'additionalProperties': True}
list_toolsets
List catalog groups with endpoint counts and short descriptions.
Use the group names as the toolset filter on search_endpoints. This
does not call the Sugra API; it reads the bundled catalog.
読み取り専用
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', 'title': 'list_toolsetsArguments', 'properties': {}}
出力スキーマ
{'type': 'object', 'title': 'list_toolsetsDictOutput', 'additionalProperties': True}
resolve_entity
Resolve free text to a canonical market or macro entity.
Turns a ticker, company name, macro indicator, coin, or currency pair into
the agent plane's ``{namespace, ids}`` entity for use with get_snapshot and
get_timeseries. A cross-namespace collision (e.g. a ticker that is both an
equity and a coin) returns status "ambiguous" with ranked candidates and
NEVER silently picks one; pass type_hint (e.g. "equity", "etf", "coin") to
narrow the universe. Crypto aliases resolve too (e.g. "bitcoin" -> the
BTC coin entity). Status "low_confidence" means the best match cleared
resolution but scored weakly - verify the returned entity before
building on it, or re-query with a more specific name or type_hint. For compliance KYB lookups by LEI/VAT or sanctions
screening use sugra_entity_lookup / sugra_entity_screen instead - this tool
is for market-data entities.
Args:
query: Free-form text - ticker, company, indicator, coin, or pair.
type_hint: Optional namespace hint narrowing resolution.
読み取り専用
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', 'title': 'resolve_entityArguments', 'required': ['query'], 'properties': {'query': {'type': 'string', 'title': 'Query'}, 'type_hint': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Type Hint', 'default': None}}}
出力スキーマ
{'type': 'object', 'title': 'resolve_entityDictOutput', 'additionalProperties': True}
search_endpoints
Search the bundled Sugra endpoint catalog by natural-language query.
Use this to pick an operation_id. It does not fetch data. Typical loop:
1. search_endpoints(query) -> ranked hits with required_parameters
2. describe_endpoint(operation_id) -> params, request_body_schema, agent_hints
3. call_endpoint(operation_id, params=..., body=...) or fetch_data(query, params=...)
Filter with toolset or source only after list_toolsets / list_sources;
a misspelled filter is an error, not a silent empty result.
Examples:
- search_endpoints("US CPI inflation")
- search_endpoints("AAPL price", toolset="markets")
- search_endpoints("container ship AIS", toolset="network")
読み取り専用
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', 'title': 'search_endpointsArguments', 'required': ['query'], 'properties': {'limit': {'type': 'integer', 'title': 'Limit', 'default': 10, 'description': 'Maximum ranked hits to return. Default 10. Does not call the Sugra API; this only bounds the catalog search list.'}, 'query': {'type': 'string', 'title': 'Query', 'description': "Natural-language search over the bundled catalog. Name the instrument, series, place, or task (examples: 'US CPI', 'AAPL quote', 'North Sea AIS'). Returns ranked operation_id hits with required_parameters. Then call describe_endpoint on a hit before call_endpoint."}, 'source': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Source', 'default': None, 'description': 'Optional source-family filter as listed by list_sources (macro, markets, ...). An unknown value returns error unknown_source with known_sources.'}, 'toolset': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Toolset', 'default': None, 'description': 'Optional catalog group filter (markets, macro, news, network, ...). Call list_toolsets for the live names. An unknown value returns error unknown_toolset with known_toolsets rather than an empty hit list.'}}}
出力スキーマ
{'type': 'object', 'title': 'search_endpointsDictOutput', 'additionalProperties': True}
sugra_entity_lookup
Resolve an entity by identifier and return its composed KYB envelope.
`anchor` is `lei` (Legal Entity Identifier, resolved via the GLEIF registry)
or `vat` (EU VAT number, validated via the EU VIES service). The result
weaves identity, a sanctions screening signal, and - on request - ownership
and adverse-media slices.
The screening verdict is a SCREENING SIGNAL, not a compliance determination,
and any PEP / adverse-media content is supplementary and non-comprehensive.
The `disclaimer` field carries this and is always present.
Output is COMPACT by default to protect the agent context budget:
`{entity:{name, anchor, value, status, country}, screening:{status,
top_matches:[...3], hit_count}, ids:{...}, disclaimer}`. Pass `include` to
opt INTO fuller per-slice detail, e.g.
`include=["ownership","adverse_media"]` adds those slices in full form.
On a bad anchor or an API error this returns a clean `{error, detail}` dict
rather than raising, so the agent can branch on `result.get("error")`.
Args:
anchor: Identifier type, one of `lei` or `vat`.
value: The identifier value (the 20-char LEI code or the VAT number).
include: Optional list of fuller slices to add, e.g.
`["ownership", "adverse_media"]`. Omit for the compact default.
読み取り専用
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', 'title': 'sugra_entity_lookupArguments', 'required': ['anchor', 'value'], 'properties': {'value': {'type': 'string', 'title': 'Value', 'description': 'The identifier value: 20-character LEI or the VAT number.'}, 'anchor': {'enum': ['lei', 'vat'], 'type': 'string', 'title': 'Anchor', 'description': 'Identifier type: lei (GLEIF) or vat (EU VIES).'}, 'include': {'anyOf': [{'type': 'array', 'items': {'type': 'string'}}, {'type': 'null'}], 'title': 'Include', 'default': None, 'description': 'Optional fuller slices to add, e.g. ownership, adverse_media. Omit for the compact default. profile and screening are already in the compact core and are not extra slices.'}}}
出力スキーマ
{'type': 'object', 'title': 'sugra_entity_lookupDictOutput', 'additionalProperties': True}
sugra_entity_screen
Screen a person or organization name against the Sugra sanctions corpus.
Returns a SCREENING SIGNAL, not a compliance determination. Sugra is a
technology provider, not a sanctions authority or consumer reporting agency.
PEP and adverse-media coverage is supplementary and non-comprehensive - a
`clear` result is not proof of absence, and a `hit` is a candidate match to
review, not a finding.
Output is COMPACT to protect the agent context budget:
`{status, matches:[{name, score, list, type}], disclaimer}`. The verdict
`status` is one of `clear`, `review`, or `hit`. The heavy raw fields
(match rationale, source ids, publish dates) are dropped; use the Sugra API
directly when the full screening envelope is needed.
Args:
name: The person or organization name to screen (required).
country: Optional ISO 3166-1 alpha-2 country to narrow the match.
dob: Optional date of birth (YYYY-MM-DD) for a person.
nationality: Optional nationality to narrow the match.
読み取り専用
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', 'title': 'sugra_entity_screenArguments', 'required': ['name'], 'properties': {'dob': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Dob', 'default': None, 'description': 'Optional date of birth for a person, YYYY-MM-DD.'}, 'name': {'type': 'string', 'title': 'Name', 'description': 'Person or organization name to screen (required).'}, 'country': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Country', 'default': None, 'description': 'Optional ISO 3166-1 alpha-2 country to narrow the match.'}, 'nationality': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Nationality', 'default': None, 'description': 'Optional nationality to narrow the match.'}}}
出力スキーマ
{'type': 'object', 'title': 'sugra_entity_screenDictOutput', 'additionalProperties': True}
履歴
最近のツール変更
削除
list_plans
2026年10月1日2:52
削除
buy_plan
2026年10月1日2:52
変更
get_snapshot
2026年10月1日2:52
変更
fetch_data
2026年10月1日2:52
変更
call_endpoint
2026年10月1日2:52
追加
buy_plan
2026年9月25日3:00
追加
list_plans
2026年9月25日3:00
追加
get_timeseries
2026年9月17日7:57
追加
get_snapshot
2026年9月17日7:57
追加
resolve_entity
2026年9月17日7:57
追加
list_sources
2026年9月17日7:57
追加
fetch_data
2026年9月17日7:57
追加
list_toolsets
2026年9月17日7:57
追加
call_endpoint
2026年9月17日7:57
追加
describe_endpoint
2026年9月17日7:57
追加
search_endpoints
2026年9月17日7:57
追加
sugra_entity_lookup
2026年9月17日7:57
追加
sugra_entity_screen
2026年9月17日7:57
関連MCP
類似のMCPサーバー
Delx Commerce — Pay-per-Result APIs for Agents
io.github.davidmosiah/delx-mcp-a2a
Provides pay-per-result APIs and agent protocol tools for continuity, multi-agent coordination, document OCR, and crypto-related …
SAP MCP Server
ai.oobeprotocol.sap.mcp/sap-mcp
Provides an MCP gateway connecting SAP-related tools with Solana, DeFi, decentralized identity, and x402 payments.
TheProtocol — Sovereign AI Agent Platform
cloud.theprotocol/registry
Manages sovereign AI agents, identities, contracts, payments, governance, exchanges, and cross-frame token transfers.
AIMEAT
io.aimeat/aimeat
Provides a self-hosted agent operating system with agent work delegation, access controls, federation, hooks, SSO, security admin…
hyperion
com.thetempleofdoom.hyperion/hyperion
Acts as a paid MCP tool marketplace and utility gateway with server discovery, HTTP and JavaScript tools, research, data conversi…
GPT55 Model Gateway
xyz.558686.gpt55/token-gateway
Acts as a remote model gateway exposing GPT chat, coding and review services, lightweight text utilities, and prepaid or x402-bas…
Rokha
ai.rokha/rokha
Provides access to an agent-skill and MCP server registry, skill inspection and composition tools, OAuth connections, and agent a…
Japan Public Ledgers MCP
com.mcp-revenue-empire/japan-public-ledgers
Provides agent identity, memory, audit, trust, proxy, temporary email, webhook, CAPTCHA, and alerting capabilities alongside publ…