agent-exec
REMOTE · AGENT-EXEC.45.67.221.128.SSLIP.IO
Accountless pay-per-use sandbox execution, storage, locks, attestation and handoff; pay via x402.
Available components
Last scanned (19 hours ago)
Scores higher than 6% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Developer Tools
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 Security57
- 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 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 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.
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.
- 28 Sept 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
- 25 Sept 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
- 21 Sept 26 −60
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.80 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 20 Sept 26 83
- Tool “service_card” rewrote its description, which is the text the model reads security
- Tool coverage: 100% → 67% ▼ functional
- Schema quality: pass → fail ▼ functional
- Destructive annotations: pass → 100 functional
- New tool “execute” functional
- 5 Sept 26 0
- Authorization: unverified → partial ▲ security
- Tool “search_listings” now declares an output schema ▲ functional
- Tool “service_card” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- 28 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 27 Aug 26 0
First indexed and scored.
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 24 Oct 2026 · Probed https://agent-exec.45.67.221.128.sslip.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agent-exec.45.67.221.128.sslip.io | CN=YE1,O=Let's Encrypt,C=US | 6 Oct 2026 | 4 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 679f4bb33819cd8d72d1988efca7998b394 |
| SANs: agent-exec.45.67.221.128.sslip.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 insecure
Validation of agent-exec.45.67.221.128.sslip.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| sslip.io. | absent | 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 | 308 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agent-exec.45.67.221.128.sslip.io/mcp | Redirected | 308 | https://agent-exec.448c.org/mcp |
| http (plaintext) | http://agent-exec.45.67.221.128.sslip.io/mcp | HTTPS enforced | 308 | https://agent-exec.45.67.221.128.sslip.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 →
execute Run code (paid, x402) ~227
PAID: run code in an isolated, network-less sandbox and get stdout, stderr and exit code back. Call it once without payment to receive the price as an x402 PaymentRequired (Base USDC, and Solana USDC where offered); call it again with a signed payment in _meta['x402/payment'] to run. The receipt comes back in _meta['x402/payment-response']. No account, no API key. Complaints, questions, quote requests, or a service you wish we had: POST /feedback on this host -- free, no account. Every report is read and analysed daily; there is no individual reply.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | – | Optional extra files, as POST /execute takes them. |
| limits | object | – | Optional limits (timeoutMs, memoryMb, ...); they set the price. |
| runtime | string | yes | Runtime name, e.g. python3 or node -- see GET /quote or the service_card tool for the list. |
| source | string | yes | The program to run. |
| stdin | string | – | Optional standard input. |
No output schema declared.
No examples provided.
search_listings Search the agent-exec directory ~111
Free, unauthenticated search over agent-exec's directory of paid agent-facing services (same data as GET https://agent-exec.45.67.221.128.sslip.io/listings). Returns a page of listings and an opaque cursor for the next page.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque pagination cursor from a previous call's nextCursor. |
| limit | integer | – | Max listings to return (server-bounded regardless). |
| tag | string | – | Filter to listings carrying this tag. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | – |
| listings | array | – | – |
| nextCursor | string|null | – | – |
No examples provided.
service_card agent-exec service card ~108
What agent-exec sells, what it costs, and exactly where to pay for it. This tool call itself is free and moves no money. Code execution can be bought right here, with the paid execute tool (x402 over MCP), or over plain HTTP at the URLs this returns. Complaints, questions, quote requests, or a service you wish we had: POST /feedback on this host -- free, no account. Every report is read and analysed daily; there is no individual reply.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | – |
| directory | object | yes | – |
| execute | object | yes | – |
| llmsTxt | string | yes | – |
| network | string | yes | – |
| openapi | string | yes | – |
| payment | object | yes | – |
| quote | object | yes | – |
| resources | array | yes | – |
| service | string | yes | – |
No examples provided.
How do I install the agent-exec MCP server?
agent-exec is a hosted endpoint at https://agent-exec.45.67.221.128.sslip.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 · agent-exec.45.67.221.128.sslip.io
claude mcp add --transport http io-sslip-128-221-67-45-agent-exec-agent-exec 'https://agent-exec.45.67.221.128.sslip.io/mcp'
What is the agent-exec MCP server?
agent-exec is an MCP server listed in the public MCP registry as io.sslip.128.221.67.45.agent-exec/agent-exec. Accountless pay-per-use sandbox execution, storage, locks, attestation and handoff; pay via x402. This page covers its hosted endpoint (https://agent-exec.45.67.221.128.sslip.io/mcp).
Is the agent-exec MCP server safe to use?
agent-exec scores 23 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 agent-exec MCP server expose?
agent-exec exposes 3 tools: execute, service_card, search_listings. Their descriptions and schemas cost roughly 446 tokens of context every time the server is loaded.
Does the agent-exec MCP server require authentication?
Its publisher declares no required credentials for agent-exec. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the agent-exec MCP server still maintained?
agent-exec is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.