Local MCP capabilities provider for Expo
Nothing to run from here
Castle is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
14
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Investigate security events and manage the allow/deny lists an analyst acts on.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http castle-mcp https://castle.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# castle_get_events_schema, castle_search_events, castle_group_events and 11 more
Castle costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http castle-mcp https://castle.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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, $ncontains |
| query_type | string | no | Return matching records, just a count, or both. Defaults to records. |
| columns | array | no | Only return these event fields. |
| page | integer | no | 1-based page number. |
| results_size | integer | no | Results per page, 1-100. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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, $ncontains |
| group_by_fields | array | yes | Fields to group by, e.g. ["ip", "user.email"]. Names come from the event schema. |
| page | integer | no | 1-based page number. |
| results_size | integer | no | Results per page, 1-100. |
Find the allow/deny lists defined in the environment. Read-only despite being a POST. Castle: POST /v1/lists/query.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| filters | array | no | Optional {field, op, value} filters over the lists themselves. |
| page | integer | no | 1-based page number. |
| results_size | integer | no | Results per page, 1-100. |
Fetch a single list with its primary and secondary field definitions. Castle: GET /v1/lists/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | The list's id. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | The list to search. |
| filters | array | no | Optional {field, op, value} filters over the items. |
| page | integer | no | 1-based page number. |
| results_size | integer | no | Results per page, 1-100. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | The list to count. |
| filters | array | no | Optional {field, op, value} filters over the items. |
Fetch a single list entry — its value, who added it, the comment and its archive time. Castle: GET /v1/lists/{list_id}/items/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | The list holding the item. |
| item_id | string | yes | The item's id. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The list name. |
| color | string | yes | Dashboard colour label, e.g. $red, $green, $blue — Castle requires one. |
| primary_field | string | yes | The event field entries match on, e.g. ip or user.email. |
| description | string | no | What this list is for. |
| secondary_field | string | no | An optional second field entries also carry. |
Rename a list or change its colour or description. Castle: PUT /v1/lists/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | The list to update. |
| name | string | no | New name. |
| color | string | no | New colour label. |
| description | string | no | New description. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | The list to add to. |
| primary_value | string | yes | The value to add, matching the list's primary_field. |
| author_type | string | yes | What kind of actor is adding this entry. |
| author_identifier | string | yes | Who is adding it, e.g. the analyst's email address. |
| secondary_value | string | no | Value for the list's secondary_field. |
| comment | string | no | Why this entry was added. |
| auto_archives_at | string | no | ISO-8601 time to archive the entry automatically. |
Change the comment on a list entry. Castle: PUT /v1/lists/{list_id}/items/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | The list holding the item. |
| item_id | string | yes | The item to update. |
| comment | string | yes | The new comment. |
Archive a list entry so it stops matching. Reversible with castle_unarchive_list_item. Castle: DELETE /v1/lists/{list_id}/items/{id}/archive.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | The list holding the item. |
| item_id | string | yes | The item to archive. |
Restore a previously archived list entry so it matches again. Castle: PUT /v1/lists/{list_id}/items/{id}/unarchive.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | The list holding the item. |
| item_id | string | yes | The item to restore. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Castle or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.1.
1.11.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Castle can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.