AgentsPodium Hosting
REMOTE · MCP.AGENTSPODIUM.COM · SCANNED SEP 23
Create, watch, pay for and connect hosted AI agent pods on AgentsPodium. Needs an API key.
Available components
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 Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1221 tokens (~87/item across 14 items; 13 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the AgentsPodium Hosting MCP server?
AgentsPodium Hosting is a hosted endpoint at https://mcp.agentspodium.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.
remote · mcp.agentspodium.com
claude mcp add --transport http com-agentspodium-hosting 'https://mcp.agentspodium.com/mcp'
{
"mcpServers": {
"com-agentspodium-hosting": {
"url": "https://mcp.agentspodium.com/mcp"
}
}
} {
"servers": {
"com-agentspodium-hosting": {
"type": "http",
"url": "https://mcp.agentspodium.com/mcp"
}
}
} [mcp_servers.com-agentspodium-hosting] url = "https://mcp.agentspodium.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-agentspodium-hosting": {
"type": "remote",
"url": "https://mcp.agentspodium.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-agentspodium-hosting --url 'https://mcp.agentspodium.com/mcp' --transport streamable-http
mcp_servers:
com-agentspodium-hosting:
url: "https://mcp.agentspodium.com/mcp" {
"McpServers": {
"com-agentspodium-hosting": {
"Transport": "http",
"Url": "https://mcp.agentspodium.com/mcp"
}
}
} assistant mcp add com-agentspodium-hosting -t streamable-http -u 'https://mcp.agentspodium.com/mcp'
{
"mcpServers": {
"com-agentspodium-hosting": {
"type": "http",
"url": "https://mcp.agentspodium.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +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.
- 20 Sept 26 0
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → fail ▼ security
- HTTPS: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Stability: unverified → 0.40 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 19 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: 0.33 → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
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 23 Sept 2026 · Probed https://mcp.agentspodium.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agentspodium.com | CN=YE2,O=Let's Encrypt,C=US | 27 Aug 2026 | 25 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5fba443068412ce0e49a7651a2d9f94567a |
| SANs: *.agentspodium.com, agentspodium.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 mcp.agentspodium.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| agentspodium.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.agentspodium.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.agentspodium.com/mcp | Inconclusive | 405 |
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 →
create_instance Create instance ~310
Create (deploy) a new AgentsPodium instance. Returns the instance id and, when enableA2A is true, the a2aUrl and a2aToken the caller should keep. After creating, poll get_instance_health until it is serving, then call set_llm_key to give it a working LLM key.
| Name | Type | Req | Description |
|---|---|---|---|
| channels | array | – | Channels to enable (web, telegram, ...). |
| domain | string | – | Customer-owned domain to serve the instance from. |
| enableA2A | boolean | – | Turn on the A2A toolset and issue an a2aUrl/a2aToken for this instance. |
| engine | string | – | Runtime engine id (e.g. hermes, openclaw, n8n). See list_platforms for what's available. |
| extraSoul | string | – | Extra system-prompt instructions appended to the persona. |
| model | string | – | Default LLM model id for the engine. |
| name | string | – | Display name for the instance. |
| personaId | string | – | Persona/template id from list_platforms; defaults to the general-purpose persona. |
| tier | string | yes | Hosting plan controlling RAM/CPU/disk. See list_platforms for prices. |
| webhookUrl | string | – | Public http(s) URL to receive signed pod events (agent.running, agent.stopped, agent.failed, agent.deleted, payment.confirmed, deletion.warning) instead of polling. The signing secret comes back once… |
| Name | Type | Req | Description |
|---|---|---|---|
| a2aToken | string|null | yes | A2A bearer token to keep, or null if A2A was not enabled. |
| a2aUrl | string|null | yes | A2A endpoint, or null if A2A was not enabled. |
| endpointUrl | string|null | yes | Public HTTPS endpoint, or null until assigned. |
| id | string | yes | Newly created instance id. |
| next | string | yes | Suggested next step for the caller. |
| status | string | yes | Initial lifecycle status. |
| webhookSecret | string|null | yes | HMAC key for webhook signatures when webhookUrl was given (shown once), else null. |
No examples provided.
delete_instance Delete instance ~40
Permanently delete an instance. This cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Instance (agent) id, as returned by create_instance or list_instances. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Id of the deleted instance. |
| ok | boolean | yes | Always true on success. |
No examples provided.
get_instance_health Check instance health ~46
Check whether an instance is reachable and serving, plus its status and quota state.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Instance (agent) id, as returned by create_instance or list_instances. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Instance id checked. |
| quotaStatus | string|null | yes | Usage quota status, or null if not tracked. |
| reachable | boolean|null | yes | Whether the instance's endpoint responded, or null if unknown. |
| serving | boolean|null | yes | Whether the instance is currently answering requests, or null if unknown. |
| status | string | yes | Lifecycle status reported by the account API. |
No examples provided.
get_instance_term Get billing term ~53
Get the billing term (trial/paid/grace) for an instance, including when it renews or expires.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Instance (agent) id, as returned by create_instance or list_instances. |
| Name | Type | Req | Description |
|---|---|---|---|
| term | object | yes | Billing term details (status, renewal/expiry dates, etc.), as returned by the account API. |
No examples provided.
get_payment_options Get payment options ~70
Get ways to pay for an instance's plan: card/subscription buy links, crypto payment info, and Telegram Stars info (crypto and Stars are in beta testing), plus the instance's current term.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Instance (agent) id, as returned by create_instance or list_instances. |
| Name | Type | Req | Description |
|---|---|---|---|
| crypto | object | yes | Crypto payment info (beta testing), as returned by the account API, plus an added 'note' field. |
| providers | – | – | Card/subscription payment providers and buy links, as returned by the account API. |
| stars | object | yes | Telegram Stars payment info (beta testing), as returned by the account API, plus an added 'note' field. |
| term | – | – | The instance's current billing term. |
No examples provided.
list_instances List instances ~45
List the caller's AgentsPodium instances (agents): id, name, engine, tier, status, endpoint and A2A URL, domain, creation date. Never returns secrets.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| instances | array | yes | The caller's instances. |
No examples provided.
list_platforms List platforms and plans ~30
List available AgentsPodium engines (platforms) and hosting plans (tiers), with prices and capabilities.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| engines | array | yes | Available runtime engines. |
| tiers | array | yes | Available hosting plans (tiers) with prices, as published by the account API. |
No examples provided.
pause_instance Pause instance ~47
Pause an instance: stops it and its billing lease. Data is archived, not deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Instance (agent) id, as returned by create_instance or list_instances. |
| Name | Type | Req | Description |
|---|---|---|---|
| a2aUrl | string|null | yes | A2A JSON-RPC endpoint for the instance, or null if A2A is not enabled. |
| createdAt | string | yes | ISO timestamp when the instance was created. |
| domain | string|null | yes | Customer-owned domain serving the instance, or null. |
| endpointUrl | string|null | yes | Public HTTPS endpoint for the instance, or null if not yet assigned. |
| engine | string | yes | Runtime engine id (e.g. hermes). |
| id | string | yes | Instance (agent) id. |
| name | string | yes | Display name. |
| status | string | yes | Lifecycle status (e.g. running, stopped). |
| tier | string | yes | Hosting plan id. |
No examples provided.
rebuild_instance Rebuild instance ~48
Rebuild an instance's pod (e.g. after a config change that needs a restart).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Instance (agent) id, as returned by create_instance or list_instances. |
| Name | Type | Req | Description |
|---|---|---|---|
| a2aUrl | string|null | yes | A2A JSON-RPC endpoint for the instance, or null if A2A is not enabled. |
| createdAt | string | yes | ISO timestamp when the instance was created. |
| domain | string|null | yes | Customer-owned domain serving the instance, or null. |
| endpointUrl | string|null | yes | Public HTTPS endpoint for the instance, or null if not yet assigned. |
| engine | string | yes | Runtime engine id (e.g. hermes). |
| id | string | yes | Instance (agent) id. |
| name | string | yes | Display name. |
| status | string | yes | Lifecycle status (e.g. running, stopped). |
| tier | string | yes | Hosting plan id. |
No examples provided.
resume_instance Resume instance ~41
Resume a previously paused instance, rebuilding it from its archive.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Instance (agent) id, as returned by create_instance or list_instances. |
| Name | Type | Req | Description |
|---|---|---|---|
| a2aUrl | string|null | yes | A2A JSON-RPC endpoint for the instance, or null if A2A is not enabled. |
| createdAt | string | yes | ISO timestamp when the instance was created. |
| domain | string|null | yes | Customer-owned domain serving the instance, or null. |
| endpointUrl | string|null | yes | Public HTTPS endpoint for the instance, or null if not yet assigned. |
| engine | string | yes | Runtime engine id (e.g. hermes). |
| id | string | yes | Instance (agent) id. |
| name | string | yes | Display name. |
| status | string | yes | Lifecycle status (e.g. running, stopped). |
| tier | string | yes | Hosting plan id. |
No examples provided.
set_llm_key Set LLM key ~135
Set (or clear, with key=null) the LLM provider API key an instance uses to answer. Required before a freshly created instance can actually respond.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Instance (agent) id, as returned by create_instance or list_instances. |
| key | string | yes | The provider API key. Stored encrypted, never echoed back. |
| model | string | – | Model id to use with this provider (e.g. gpt-4o-mini). Optional; the engine defaults if omitted. |
| provider | string | yes | LLM provider id, e.g. openai, anthropic, deepseek. |
| Name | Type | Req | Description |
|---|---|---|---|
| a2aUrl | string|null | yes | A2A JSON-RPC endpoint for the instance, or null if A2A is not enabled. |
| createdAt | string | yes | ISO timestamp when the instance was created. |
| domain | string|null | yes | Customer-owned domain serving the instance, or null. |
| endpointUrl | string|null | yes | Public HTTPS endpoint for the instance, or null if not yet assigned. |
| engine | string | yes | Runtime engine id (e.g. hermes). |
| id | string | yes | Instance (agent) id. |
| name | string | yes | Display name. |
| status | string | yes | Lifecycle status (e.g. running, stopped). |
| tier | string | yes | Hosting plan id. |
No examples provided.
set_peers Set A2A peers ~67
Set the list of other A2A agents this instance is allowed to call by name.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Instance (agent) id whose peer list is being set. |
| peers | array | yes | Full replacement list of peer agents this instance may call (up to 20). |
| Name | Type | Req | Description |
|---|---|---|---|
| a2aUrl | string|null | yes | A2A JSON-RPC endpoint for the instance, or null if A2A is not enabled. |
| createdAt | string | yes | ISO timestamp when the instance was created. |
| domain | string|null | yes | Customer-owned domain serving the instance, or null. |
| endpointUrl | string|null | yes | Public HTTPS endpoint for the instance, or null if not yet assigned. |
| engine | string | yes | Runtime engine id (e.g. hermes). |
| id | string | yes | Instance (agent) id. |
| name | string | yes | Display name. |
| status | string | yes | Lifecycle status (e.g. running, stopped). |
| tier | string | yes | Hosting plan id. |
No examples provided.
set_webhook Set event webhook ~103
Register a URL that receives signed POSTs when the instance comes up, stops, fails, is deleted, when a payment is confirmed and before deletion for non-payment — instead of polling get_instance_health. Returns the HMAC secret once.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Instance (agent) id, as returned by create_instance or list_instances. |
| url | string | yes | Public http(s) URL to POST signed pod events to. Private and loopback hosts are refused. |
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | yes | Event types that will be delivered. |
| id | string | yes | Instance id. |
| secret | string | yes | HMAC-SHA256 key for X-AgentsPodium-Signature. Shown once — store it. |
| url | string | yes | The webhook URL now in effect. |
No examples provided.
What is the AgentsPodium Hosting MCP server?
AgentsPodium Hosting is an MCP server listed in the public MCP registry as com.agentspodium/hosting. Create, watch, pay for and connect hosted AI agent pods on AgentsPodium. Needs an API key. This page covers its hosted endpoint (https://mcp.agentspodium.com/mcp).
Is the AgentsPodium Hosting MCP server safe to use?
AgentsPodium Hosting scores 79 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 AgentsPodium Hosting MCP server expose?
AgentsPodium Hosting exposes 13 tools: list_platforms, list_instances, create_instance, get_instance_health, get_instance_term, and 8 more. Their descriptions and schemas cost roughly 1,035 tokens of context every time the server is loaded.
Does the AgentsPodium Hosting MCP server require authentication?
Yes. AgentsPodium Hosting asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the AgentsPodium Hosting MCP server still maintained?
AgentsPodium Hosting is still listed as active in the MCP registry. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.