# Toolcard (remote · agentghostedme.com)

Cited checks for one MCP tool or a tools list, plus a called-or-ignored tally.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `agentghostedme.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-agentghostedme-toolcard/agentghostedme.md), [page](https://verifymcp.io/servers/com-agentghostedme-toolcard/agentghostedme)

## Channel facts

- Endpoint: `https://agentghostedme.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.8`

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

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 716 tokens (~102/item across 7 items; 4 tools + 3 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Toolcard MCP server?

Toolcard is a hosted endpoint at https://agentghostedme.com/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 com-agentghostedme-toolcard 'https://agentghostedme.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-agentghostedme-toolcard": {
      "url": "https://agentghostedme.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-agentghostedme-toolcard": {
      "type": "http",
      "url": "https://agentghostedme.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-agentghostedme-toolcard]
url = "https://agentghostedme.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-agentghostedme-toolcard --url 'https://agentghostedme.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-agentghostedme-toolcard:
    url: "https://agentghostedme.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-agentghostedme-toolcard": {
      "Transport": "http",
      "Url": "https://agentghostedme.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-agentghostedme-toolcard -t streamable-http -u 'https://agentghostedme.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-agentghostedme-toolcard": {
      "type": "http",
      "url": "https://agentghostedme.com/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-04 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

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

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

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

### 2026-10-20 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (4)

### `check_tool` (~96 tokens)

Check one MCP tool definition

Check one MCP tool name, description, and input schema against Toolcard cited rules. Returns findings. A finding with an answer page includes resource, a toolcard://answers URI to pass to resources/read. Does not store the tool.

Input parameters:

- `description` (string): Description shown to the model
- `inputSchema` (object): JSON Schema object for the tool arguments
- `name` (string, required): Tool name, for example manage_user

### `check_server` (~103 tokens)

Check a tools/list result

Check every tool in a tools/list result or a server card. Returns per-tool findings plus duplicate-name, overlapping-descriptions, and too-many-tools. Those three omit resource. Does not store the tools.

Input parameters:

- `result` (object): JSON-RPC tools/list result. Used only when tools is omitted. The array is result.tools.
- `tools` (array): Tools from a tools/list result or a server card. Each item has name, description, and inputSchema.

### `report_outcome` (~130 tokens)

Report whether a tool was called

Record whether an agent called or ignored a tool. Stores the name, a SHA-256 of the description, and the result. Does not store the raw description.

Input parameters:

- `client` (string): Optional short label such as cursor. No account ids.
- `description` (string): Hashed with SHA-256 and not stored
- `name` (string, required): Tool name that was offered to the agent
- `report_id` (string): Optional idempotency key, 8 to 80 letters, digits, underscore or hyphen
- `result` (string, required): Whether an agent called the tool

### `outcome_summary` (~26 tokens)

Read the call tally

Return the anonymous tally of called versus ignored reports on this server. Not a representative sample.

## Diagnostics

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

## Score history

- 2026-11-05: 80
- 2026-11-04: 80
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 77
- 2026-10-29: 77
- 2026-10-28: 76
- 2026-10-27: 76
- 2026-10-26: 75
- 2026-10-25: 75
- 2026-10-24: 75
- 2026-10-23: 74
- 2026-10-22: 74
- 2026-10-21: 73
- 2026-10-20: 73
- 2026-10-19: 72

## Common questions

### What is the Toolcard MCP server?

Toolcard is an MCP server listed in the public MCP registry as com.agentghostedme/toolcard. Cited checks for one MCP tool or a tools list, plus a called-or-ignored tally. This page covers its hosted endpoint (https://agentghostedme.com/mcp).

### Is the Toolcard MCP server safe to use?

Toolcard scores 80 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 Toolcard MCP server expose?

Toolcard exposes 4 tools: check_tool, check_server, report_outcome, outcome_summary. Their descriptions and schemas cost roughly 355 tokens of context every time the server is loaded.

### Does the Toolcard MCP server require authentication?

No. We connected to Toolcard without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Toolcard MCP server still maintained?

Toolcard is still listed as active in the MCP registry. We last reached this channel on 5 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://agentghostedme.com/mcp
- Website: https://agentghostedme.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-agentghostedme-toolcard/agentghostedme.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-agentghostedme-toolcard/agentghostedme.json
- HTML version of this page: https://verifymcp.io/servers/com-agentghostedme-toolcard/agentghostedme