Skip to content

InfraPulse MCP server

ai.infrapulse/infrapulseinfrapulse.aistreamable-httpv1.0.1Scanned

AI agent infrastructure for discovery, authorization, execution, identity, and signed receipts.

6 tools: 1 can delete or cancel things, 4 change things and 1 only read.

Tools: 1 delete, 0 irreversible, 4 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the InfraPulse MCP server can do

The InfraPulse MCP server is published by infrapulse.ai, a domain the MCP Registry verified. It has 6 tools. It can delete or cancel things (1 tool: execute) and create or change data (4 tools: discover, connect, authorize and verify_receipt). 1 tool only reads.

1 tool brings in text other people can write (execute).

The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 11, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Deletes or cancels 1Claude Code: deny
  • executeExecute authorized provider work through InfraPulse.Reads text others writeNo findings

    Why it is in this group

    • The name "execute" says "execute": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: true
    • idempotentHint: true
Changes things 4Claude Code: ask
  • authorizeCreate an idempotent prepaid authorization for a quoted operation.No findings

    Why it is in this group

    • The description's first verb is "create": a word for a change.
    Description, as the server wrote it
    Create an idempotent prepaid authorization for a quoted operation. This may reserve private account credits but does not execute provider work.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • connectConnect an InfraPulse identity to the MCP workflow.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...rned ipc_live_ bearer directly; machine credentials do not require a human OAuth approval s..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • discoverDiscover InfraPulse production capabilities and optional read-only audit views: readiness, safe_checks, test_catalog, and evidence.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Discover InfraPulse production capabilities and optional read-only audit views: readiness, safe_checks, test_catalog, and evidence. Does not authorize providers, spend credits, change accounts, or publish releases.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • verify_receiptVerify an InfraPulse signed receipt by receipt_id or receipt object without changing account or provider state.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Verify an InfraPulse signed receipt by receipt_id or receipt object without changing account or provider state.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
Only reads 1Show 1 read-only tool
  • quoteGet a deterministic price quote before authorization or execution.No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    Get a deterministic price quote before authorization or execution. This does not reserve credits or run provider work.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:26 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://infrapulse.ai/.well-known/oauth-protected-resource/mcp
Authorization servers
https://infrapulse.ai
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (1 destructive, 4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://infrapulse.ai/mcp: tools/list returned 6 tools to an anonymous client, including execute (destructive), discover (write), connect (write), authorize (write), verify_receipt (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The description mentions "credentials".

    Matched text

    description: "...rned ipc_live_ bearer directly; machine credentials do not require a human OAuth approval s..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools4 changed.~4 changedView diff
    • Changed:authorizeChanges thingsinputSchema
    • Changed:discoverChanges thingsdescriptioninputSchema
    • Changed:executeDeletes or cancelsinputSchema
    • Changed:quoteOnly readsinputSchema

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http infrapulse https://infrapulse.ai/mcp
claude mcp add --transport http infrapulse https://infrapulse.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__infrapulse__quote"
    ],
    "ask": [
      "mcp__infrapulse__discover",
      "mcp__infrapulse__connect",
      "mcp__infrapulse__authorize",
      "mcp__infrapulse__verify_receipt"
    ],
    "deny": [
      "mcp__infrapulse__execute"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as infrapulse. Review it before you use it.

Capability tags behind 1 rule
  • mcp__infrapulse__execute untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.infrapulse/infrapulse/verify?hash=9bb47ab3fea187d8634234c2bb9d37ce46c0aa198ee48902eba92e6b40a9d1d9" | jq -e '.changed == false'

Pinned hash 9bb47ab3fea1, from Nov 11, 2026, 19:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.infrapulse/infrapulse/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.infrapulse/infrapulse
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.infrapulse/infrapulse.svg)](https://radar.anlyon.com/servers/ai.infrapulse/infrapulse)

Source: MCP Registry. Synced Oct 21, 2026, 17:41 UTC.

InfraPulse MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the InfraPulse MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 5 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the InfraPulse MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: execute.

Can the InfraPulse MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the InfraPulse MCP server have?

6 tools: 1 destructive, 4 write, 1 read. execute, discover, connect, authorize, verify_receipt and quote.

Does the InfraPulse MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the InfraPulse MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the InfraPulse MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.