InfraPulse
REMOTE · INFRAPULSE.AI · SCANNED OCT 4
AI agent infrastructure for discovery, authorization, execution, identity, and signed receipts.
Available components
Recent critical change
Authorization (27 Sept 2026). See the changelog before you install this server.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (execute). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 595 tokens (~99/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 42% of tool parameters carry a description.Partial
- 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 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the InfraPulse MCP server?
InfraPulse is a hosted endpoint at https://infrapulse.ai/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 · infrapulse.ai
claude mcp add --transport http ai-infrapulse-infrapulse 'https://infrapulse.ai/mcp'
{
"mcpServers": {
"ai-infrapulse-infrapulse": {
"url": "https://infrapulse.ai/mcp"
}
}
} {
"servers": {
"ai-infrapulse-infrapulse": {
"type": "http",
"url": "https://infrapulse.ai/mcp"
}
}
} [mcp_servers.ai-infrapulse-infrapulse] url = "https://infrapulse.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-infrapulse-infrapulse": {
"type": "remote",
"url": "https://infrapulse.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-infrapulse-infrapulse --url 'https://infrapulse.ai/mcp' --transport streamable-http
mcp_servers:
ai-infrapulse-infrapulse:
url: "https://infrapulse.ai/mcp" {
"McpServers": {
"ai-infrapulse-infrapulse": {
"Transport": "http",
"Url": "https://infrapulse.ai/mcp"
}
}
} assistant mcp add ai-infrapulse-infrapulse -t streamable-http -u 'https://infrapulse.ai/mcp'
{
"mcpServers": {
"ai-infrapulse-infrapulse": {
"type": "http",
"url": "https://infrapulse.ai/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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +52
- Authorization: unverified → fail ▼ critical
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ 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
- 17 Sept 26 −49
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.77 → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 15 Sept 26 +49
- Authorization: unverified → fail ▼ critical
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.73 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 12 Sept 26 −47
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.60 → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 11 Sept 26 +47
- Authorization: unverified → fail ▼ critical
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.60 ▲ functional
- 10 Sept 26 −46
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.53 → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ 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 4 Oct 2026 · Probed https://infrapulse.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=infrapulse.ai | CN=WE1,O=Google Trust Services,C=US | 30 Sept 2026 | 29 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 78352fbce9aa36860ea3b0ea72957c92 |
| SANs: infrapulse.ai, *.infrapulse.ai | ||||||
| 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 infrapulse.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| infrapulse.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: https:; connect-src 'self' https:; frame-ancestors 'none'; |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://infrapulse.ai/mcp | Verified | 200 | |
| http (plaintext) | http://infrapulse.ai/mcp | HTTPS enforced | 301 | https://infrapulse.ai:443/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 →
authorize Authorize prepaid work ~93
Create an idempotent prepaid authorization for a quoted operation. This may reserve private account credits but does not execute provider work.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| credits | integer | – | – |
| payload | object | – | Optional canonical InfraPulse payload; direct top-level fields are also accepted. |
| quote_id | string | – | – |
| request_id | string | yes | Stable idempotency key for this mutating operation. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
| error | object|null | – | – |
| intent | string | – | – |
| next_action | object|null | – | – |
| ok | boolean | – | – |
| operation_id | string|null | – | – |
| receipt | object|null | – | – |
| request_id | string|null | – | – |
| requires_human | boolean | – | – |
| status | string|null | – | – |
| success | boolean | – | – |
No examples provided.
connect Connect InfraPulse account ~186
Connect an InfraPulse identity to the MCP workflow. Existing customer accounts use OAuth and explicit owner approval for operational scopes. Autonomous machines may self-register at /v1/agents/register and use the returned ipc_live_ bearer directly; machine credentials do not require a human OAuth approval step.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Follow-up action for an existing connection. Defaults to status. |
| agent_id | string | – | Required only when the OAuth identity owns multiple linked InfraPulse agents. |
| approved_scopes | array | – | Optional subset to approve when action=approve. |
| connection_id | string | – | Server-generated connection id for status or approval follow-up. |
| request_id | string | – | Stable idempotency key for a new connection request. |
| scopes | array | – | InfraPulse operational scopes requested for a new connection. These are approved and stored by InfraPulse, never copied into the OAuth token. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
| error | object|null | – | – |
| intent | string | – | – |
| next_action | object|null | – | – |
| ok | boolean | – | – |
| operation_id | string|null | – | – |
| receipt | object|null | – | – |
| request_id | string|null | – | – |
| requires_human | boolean | – | – |
| status | string|null | – | – |
| success | boolean | – | – |
No examples provided.
discover Discover InfraPulse ~22
Discover InfraPulse production capabilities and the universal execution contract without changing account state.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
| error | object|null | – | – |
| intent | string | – | – |
| next_action | object|null | – | – |
| ok | boolean | – | – |
| operation_id | string|null | – | – |
| receipt | object|null | – | – |
| request_id | string|null | – | – |
| requires_human | boolean | – | – |
| status | string|null | – | – |
| success | boolean | – | – |
No examples provided.
execute Execute authorized work ~144
Execute authorized provider work through InfraPulse. Requires a stable request_id and canonical authorization_id; may consume prepaid credits and change an external provider system.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| authorization_id | string | yes | Canonical authorization returned by the authorize step. |
| input | object | – | – |
| metadata | object | – | – |
| payload | object | – | Optional canonical InfraPulse payload; direct top-level fields are also accepted. |
| provider_id | string | – | – |
| provider_intent | string | – | – |
| request_id | string | yes | Stable idempotency key for this mutating operation. |
| task | string | – | – |
| timeout_seconds | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
| error | object|null | – | – |
| intent | string | – | – |
| next_action | object|null | – | – |
| ok | boolean | – | – |
| operation_id | string|null | – | – |
| receipt | object|null | – | – |
| request_id | string|null | – | – |
| requires_human | boolean | – | – |
| status | string|null | – | – |
| success | boolean | – | – |
No examples provided.
quote Quote InfraPulse work ~42
Get a deterministic price quote before authorization or execution. This does not reserve credits or run provider work.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| payload | object | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
| error | object|null | – | – |
| intent | string | – | – |
| next_action | object|null | – | – |
| ok | boolean | – | – |
| operation_id | string|null | – | – |
| receipt | object|null | – | – |
| request_id | string|null | – | – |
| requires_human | boolean | – | – |
| status | string|null | – | – |
| success | boolean | – | – |
No examples provided.
verify_receipt Verify InfraPulse receipt ~50
Verify an InfraPulse signed receipt by receipt_id or receipt object without changing account or provider state.
| Name | Type | Req | Description |
|---|---|---|---|
| payload | object | – | – |
| receipt | object | – | – |
| receipt_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
| error | object|null | – | – |
| intent | string | – | – |
| next_action | object|null | – | – |
| ok | boolean | – | – |
| operation_id | string|null | – | – |
| receipt | object|null | – | – |
| request_id | string|null | – | – |
| requires_human | boolean | – | – |
| status | string|null | – | – |
| success | boolean | – | – |
No examples provided.
What is the InfraPulse MCP server?
InfraPulse is an MCP server listed in the public MCP registry as ai.infrapulse/infrapulse. AI agent infrastructure for discovery, authorization, execution, identity, and signed receipts. This page covers its hosted endpoint (https://infrapulse.ai/mcp).
Is the InfraPulse MCP server safe to use?
InfraPulse scores 78 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 InfraPulse MCP server expose?
InfraPulse exposes 6 tools: discover, connect, quote, authorize, execute, verify_receipt. Their descriptions and schemas cost roughly 537 tokens of context every time the server is loaded.
Does the InfraPulse MCP server require authentication?
No. We connected to InfraPulse without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the InfraPulse MCP server still maintained?
InfraPulse is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.