Castle MCP by usefulapi
REMOTE · CASTLE.USEFULAPI.IO
Investigate security events and manage the allow/deny lists an analyst acts on.
Available components
Last scanned (21 hours ago)
Scores higher than 3% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Security
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Nov 26 −60
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.87 → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 0
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- Stability: pass → 0.83 functional
- New prompt “add_an_entry_to_a_list_or_change_its_comment” functional
- New prompt “archive_or_restore_a_list_entry” functional
- New prompt “find_which_ips_devices_or_countries_drive_a_spike” functional
- New prompt “review_recent_logins_sign_ups_and_their_risk_verdicts” functional
- New prompt “review_what_is_on_an_allow_or_deny_list” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 +1
- Server version: 1.24.0 → 1.25.0 functional
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 21 Nov 2026 · Probed https://castle.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 11 Nov 2026 | 9 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 93e2fea3bbc31354138c8a47c5e87592 |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of castle.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://castle.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/castle/ |
| http (plaintext) | http://castle.usefulapi.io/mcp | Inconclusive | 302 | http://castle.usefulapi.io/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 →
castle_archive_list_item Archive a list item ~71
Archive a list entry so it stops matching. Reversible with castle_unarchive_list_item. Castle: DELETE /v1/lists/{list_id}/items/{id}/archive.
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | string | yes | The item to archive. |
| list_id | string | yes | The list holding the item. |
No output schema declared.
No examples provided.
castle_count_list_items Count items in a list ~79
Count the entries in one list, with the same optional filters as the search. Read-only despite being a POST. Castle: POST /v1/lists/{list_id}/items/count.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | array | – | Optional {field, op, value} filters over the items. |
| list_id | string | yes | The list to count. |
No output schema declared.
No examples provided.
castle_create_list Create a list ~130
Create a new allow or deny list. primary_field is the event field its entries match on, e.g. ip or user.email. Castle: POST /v1/lists.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | yes | Dashboard colour label, e.g. $red, $green, $blue — Castle requires one. |
| description | string | – | What this list is for. |
| name | string | yes | The list name. |
| primary_field | string | yes | The event field entries match on, e.g. ip or user.email. |
| secondary_field | string | – | An optional second field entries also carry. |
No output schema declared.
No examples provided.
castle_create_list_item Add an item to a list ~162
Add an entry to a list — for example block an IP or an email. This changes live policy behaviour. Castle: POST /v1/lists/{list_id}/items.
| Name | Type | Req | Description |
|---|---|---|---|
| author_identifier | string | yes | Who is adding it, e.g. the analyst's email address. |
| author_type | string | yes | What kind of actor is adding this entry. |
| auto_archives_at | string | – | ISO-8601 time to archive the entry automatically. |
| comment | string | – | Why this entry was added. |
| list_id | string | yes | The list to add to. |
| primary_value | string | yes | The value to add, matching the list's primary_field. |
| secondary_value | string | – | Value for the list's secondary_field. |
No output schema declared.
No examples provided.
castle_get_events_schema Get the event schema ~47
List the event fields you can filter and group on, with their types. Read this first — the other query tools need real field names. Castle: GET /v1/events/schema.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
castle_get_list Get one list ~44
Fetch a single list with its primary and secondary field definitions. Castle: GET /v1/lists/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | string | yes | The list's id. |
No output schema declared.
No examples provided.
castle_get_list_item Get one list item ~70
Fetch a single list entry — its value, who added it, the comment and its archive time. Castle: GET /v1/lists/{list_id}/items/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | string | yes | The item's id. |
| list_id | string | yes | The list holding the item. |
No output schema declared.
No examples provided.
castle_group_events Group security events ~253
Aggregate matching events by one or more fields — the fast way to see which IPs, devices or countries dominate a spike. Read-only despite being a POST. Castle: POST /v1/events/group.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | array | yes | Castle query filters, ANDed together. Each is {field, op, value} — e.g. {"field":"user.email","op":"$eq","value":"a@example.com"}. Operators: $eq, $neq, $in, $nin, $like, $nlike, $contains, $ncontain… |
| group_by_fields | array | yes | Fields to group by, e.g. ["ip", "user.email"]. Names come from the event schema. |
| page | integer | – | 1-based page number. |
| results_size | integer | – | Results per page, 1-100. |
No output schema declared.
No examples provided.
castle_search_events Search security events ~258
Query the security event stream — logins, registrations, transactions and their risk verdicts. Read-only despite being a POST: Castle takes the query in the body. Castle: POST /v1/events/query.
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | – | Only return these event fields. |
| filters | array | yes | Castle query filters, ANDed together. Each is {field, op, value} — e.g. {"field":"user.email","op":"$eq","value":"a@example.com"}. Operators: $eq, $neq, $in, $nin, $like, $nlike, $contains, $ncontain… |
| page | integer | – | 1-based page number. |
| query_type | string | – | Return matching records, just a count, or both. Defaults to records. |
| results_size | integer | – | Results per page, 1-100. |
No output schema declared.
No examples provided.
castle_search_list_items Search items in a list ~110
Search the entries of one list — the blocked IPs, emails or device ids it holds. Read-only despite being a POST. Castle: POST /v1/lists/{list_id}/items/query.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | array | – | Optional {field, op, value} filters over the items. |
| list_id | string | yes | The list to search. |
| page | integer | – | 1-based page number. |
| results_size | integer | – | Results per page, 1-100. |
No output schema declared.
No examples provided.
castle_search_lists Search lists ~85
Find the allow/deny lists defined in the environment. Read-only despite being a POST. Castle: POST /v1/lists/query.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | array | – | Optional {field, op, value} filters over the lists themselves. |
| page | integer | – | 1-based page number. |
| results_size | integer | – | Results per page, 1-100. |
No output schema declared.
No examples provided.
castle_unarchive_list_item Unarchive a list item ~66
Restore a previously archived list entry so it matches again. Castle: PUT /v1/lists/{list_id}/items/{id}/unarchive.
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | string | yes | The item to restore. |
| list_id | string | yes | The list holding the item. |
No output schema declared.
No examples provided.
castle_update_list Update a list ~70
Rename a list or change its colour or description. Castle: PUT /v1/lists/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | New colour label. |
| description | string | – | New description. |
| list_id | string | yes | The list to update. |
| name | string | – | New name. |
No output schema declared.
No examples provided.
castle_update_list_item Update a list item's comment ~69
Change the comment on a list entry. Castle: PUT /v1/lists/{list_id}/items/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | yes | The new comment. |
| item_id | string | yes | The item to update. |
| list_id | string | yes | The list holding the item. |
No output schema declared.
No examples provided.
How do I install the Castle MCP by usefulapi server?
Castle MCP by usefulapi is a hosted endpoint at https://castle.usefulapi.io/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 · castle.usefulapi.io
claude mcp add --transport http io-usefulapi-castle 'https://castle.usefulapi.io/mcp'
What is the Castle MCP by usefulapi server?
Castle MCP by usefulapi is listed in the public MCP registry as io.usefulapi/castle. Investigate security events and manage the allow/deny lists an analyst acts on. This page covers its hosted endpoint (https://castle.usefulapi.io/mcp).
Is the Castle MCP by usefulapi server safe to use?
Castle MCP by usefulapi scores 18 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 Castle MCP by usefulapi server expose?
Castle MCP by usefulapi exposes 14 tools: castle_get_events_schema, castle_search_events, castle_group_events, castle_search_lists, castle_get_list, and 9 more. Their descriptions and schemas cost roughly 1,514 tokens of context every time the server is loaded.
Does the Castle MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Castle MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Castle MCP by usefulapi server still maintained?
Castle MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Castle MCP by usefulapi server?
VerifyMCP ran 4 checks on Castle MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Castle MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.