# Issuerwire — capital markets news for AI agents (remote · mcp.issuerwire.ai)

Issuerwire — capital markets news for AI agents, one signed row per filing; markets: see facts.json.

- Trust score: 67/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `mcp.issuerwire.ai`: 67/100 (this document), [markdown](https://verifymcp.io/servers/allooloo-issuerwire/mcp.md), [page](https://verifymcp.io/servers/allooloo-issuerwire/mcp)
- remote · `x402.a2a-amn.ai`: 23/100, [markdown](https://verifymcp.io/servers/allooloo-issuerwire/x402.md), [page](https://verifymcp.io/servers/allooloo-issuerwire/x402)

## Channel facts

- Endpoint: `https://mcp.issuerwire.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.4.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 60/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (fair).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http allooloo-issuerwire 'https://mcp.issuerwire.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "allooloo-issuerwire": {
      "url": "https://mcp.issuerwire.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "allooloo-issuerwire": {
      "type": "http",
      "url": "https://mcp.issuerwire.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.allooloo-issuerwire]
url = "https://mcp.issuerwire.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "allooloo-issuerwire": {
      "type": "remote",
      "url": "https://mcp.issuerwire.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add allooloo-issuerwire --url 'https://mcp.issuerwire.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  allooloo-issuerwire:
    url: "https://mcp.issuerwire.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "allooloo-issuerwire": {
      "Transport": "http",
      "Url": "https://mcp.issuerwire.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add allooloo-issuerwire -t streamable-http -u 'https://mcp.issuerwire.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "allooloo-issuerwire": {
      "type": "http",
      "url": "https://mcp.issuerwire.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 67, +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.

### 2026-11-01 (score 66, +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.

### 2026-10-30 (score 65, +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.

### 2026-10-29 (score 64, +1)

- [security improvement] DNSSEC: fail → pass

### 2026-10-28 (score 63, +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.

### 2026-10-26 (score 62, +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.

### 2026-10-25 (score 61, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-10-24 (score 61, +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.

## MCP tools (8)

### `resolve_issuer` (~102 tokens)

Resolve Issuer

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.

Input parameters:

- `limit` (integer)
- `market`
- `query` (string, required)

### `get_issuer` (~74 tokens)

Get Issuer

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.

Input parameters:

- `issuer_key` (string, required)

### `list_filings` (~86 tokens)

List Filings

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.

Input parameters:

- `issuer` (string, required)
- `limit` (integer)
- `since`
- `type`

### `get_delta` (~123 tokens)

Get Delta

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).

Input parameters:

- `issuer`
- `market`
- `since` (string)

### `get_row` (~45 tokens)

Get Row

One news row by id. Facts level open; the full signed row (source page, publisher, read date, signature) settles on x402.

Input parameters:

- `id` (string, required)

### `claim_row` (~80 tokens)

Claim Row

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.

Input parameters:

- `contact` (string, required)
- `domain` (string, required)
- `issuer_key` (string, required)

### `create_order_intent` (~74 tokens)

Create Order Intent

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.

Input parameters:

- `issuer` (string, required)
- `scope` (string)
- `since`

### `log_audit` (~65 tokens)

Log Audit

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.

Input parameters:

- `kind` (string, required)
- `note`
- `reference_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/allooloo-issuerwire/mcp#diagnostics

## Score history

- 2026-11-04: 67
- 2026-11-03: 67
- 2026-11-02: 66
- 2026-11-01: 66
- 2026-10-31: 65
- 2026-10-30: 65
- 2026-10-29: 64
- 2026-10-28: 63
- 2026-10-27: 62
- 2026-10-26: 62
- 2026-10-25: 61
- 2026-10-24: 61
- 2026-10-23: 60
- 2026-10-22: 60
- 2026-10-21: 60

## Common questions

### 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.

## Links

- Remote endpoint: https://mcp.issuerwire.ai/mcp
- Website: https://issuerwire.ai/
- Changelog RSS feed: https://verifymcp.io/servers/allooloo-issuerwire/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/allooloo-issuerwire/mcp.json
- HTML version of this page: https://verifymcp.io/servers/allooloo-issuerwire/mcp