Issuerwire — capital markets news for AI agents
REMOTE · MCP.ISSUERWIRE.AI · 2 COMPONENTS
Issuerwire — capital markets news for AI agents, one signed row per filing; markets: see facts.json.
Available components
Last scanned (21 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 919 tokens (~114/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
- DNSSEC: fail → pass ▲ security
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://mcp.issuerwire.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=issuerwire.ai | CN=YE2,O=Let's Encrypt,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6ac0d1378a3136c7494d3c7379624dfa289 |
| SANs: *.issuerwire.ai, issuerwire.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.issuerwire.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| issuerwire.ai. | present | 2371 | 13 | Verified |
| mcp.issuerwire.ai. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.issuerwire.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.issuerwire.ai/mcp | HTTPS enforced | 301 | https://mcp.issuerwire.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
claim_row Claim Row ~80
An issuer claims its row, free: the issuer's domain and a contact; the nightly claims rail reads the domain and the row moves listed → claimed (verified when the domain answers on its cadence). A claim that stops answering falls back to listed.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | yes | – |
| domain | string | yes | – |
| issuer_key | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
create_order_intent Create Order Intent ~74
An order intent for a paid read (the full row or the delta): returns the x402 terms for mcp.issuerwire.ai and the intent id to carry into the paid call. Nothing is sold but the read.
| Name | Type | Req | Description |
|---|---|---|---|
| issuer | string | yes | – |
| scope | string | – | – |
| since | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_delta Get Delta ~123
What has this issuer filed or released since my last read? Pass the instant (or date) of your last read — for one issuer, or for a whole market with market=US·UK·CA·DE·FR·NL·CH·AU·SG·JP·KR·HK and no issuer; the signed delta — every new row with its source page and the delta envelope signed — settles on x402 inside the call. Open at the facts level (count and ids).
| Name | Type | Req | Description |
|---|---|---|---|
| issuer | – | – | – |
| market | – | – | – |
| since | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_issuer Get Issuer ~74
One issuer row by issuer_key. Open at the facts level (name, tickers, identifiers, status, claim standing, how many rows the record holds for it); the full signed row — every field with its source page and read date — settles on x402 inside the call.
| Name | Type | Req | Description |
|---|---|---|---|
| issuer_key | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_row Get Row ~45
One news row by id. Facts level open; the full signed row (source page, publisher, read date, signature) settles on x402.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_filings List Filings ~86
The news rows the record holds for an issuer: filings, releases and third-party coverage, newest first, from a date. Open at the facts level (id, date, type, title, counts); the signed rows with their source pages settle on x402.
| Name | Type | Req | Description |
|---|---|---|---|
| issuer | string | yes | – |
| limit | integer | – | – |
| since | – | – | – |
| type | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
log_audit Log Audit ~65
Write a signed audit line to the ledger (kinds: read · claim · order_intent · note) for a reference id from this door; returns the ledger event id.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | – |
| note | – | – | – |
| reference_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
resolve_issuer Resolve Issuer ~102
Who is this issuer? A name, ticker, ISIN, LEI, CIK or Companies House number (optionally a market: US · UK · CA · DE · FR · NL · CH · AU · SG · JP · KR · HK) resolves to the issuer keys on the record, with name, tickers, status and claim standing. Open.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| market | – | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Issuerwire — capital markets news for AI agents MCP server?
Issuerwire — capital markets news for AI agents is a hosted endpoint at https://mcp.issuerwire.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.issuerwire.ai
claude mcp add --transport http allooloo-issuerwire 'https://mcp.issuerwire.ai/mcp'
What is the Issuerwire — capital markets news for AI agents MCP server?
Issuerwire — capital markets news for AI agents is an MCP server listed in the public MCP registry as io.github.allooloo/issuerwire. Issuerwire, capital markets news for AI agents, one signed row per filing; markets: see facts.json. This page covers its hosted endpoint (https://mcp.issuerwire.ai/mcp).
Is the Issuerwire — capital markets news for AI agents MCP server safe to use?
Issuerwire — capital markets news for AI agents scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Issuerwire — capital markets news for AI agents MCP server expose?
Issuerwire — capital markets news for AI agents exposes 8 tools: resolve_issuer, get_issuer, list_filings, get_delta, get_row, and 3 more. Their descriptions and schemas cost roughly 649 tokens of context every time the server is loaded.
Does the Issuerwire — capital markets news for AI agents MCP server require authentication?
No. We connected to Issuerwire — capital markets news for AI agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Issuerwire — capital markets news for AI agents MCP server still maintained?
Issuerwire — capital markets news for AI agents is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.