RMCP.DEV
← Registry

API Tools

infaris.com

Provides developer resources and guidance for the Infaris Guard monitoring API, including OpenAPI specs, OAuth scopes, MCP endpoints, and CLI/webhook details.

2 endpoints8 known toolsFirst detected October 15, 2026Last detected October 15, 2026

ENDPOINT 1

https://infaris.com/.well-known/mcp

No auth detected

MCP server metadata

Name
infaris
Version
1.0.0
Capabilities
toolsresources
Server instructions

Infaris public MCP server. Use it to learn what Infaris is, when to reach for Guard, and where OpenAPI, OAuth, the Guard MCP server, and the CLI live. It is read-only and needs no authentication. When to use: identity discovery, product orientation, developer-resource lookup. When not to use: live uptime data, creating monitors, or mutating a tenant. Those jobs belong on https://api.ipulse.one/mcp with read/write OAuth scopes, or the Guard CLI. Handshake: GET https://infaris.com/.well-known/mcp. JSON-RPC: POST https://infaris.com/.well-known/mcp or POST https://infaris.com/mcp.

Known tools 4

infaris_get_overview

Return a short overview of Infaris and its monitoring product Guard, with links to OpenAPI, MCP and docs.

Inferred read-only
infaris_get_developer_docs

Return Infaris developer resources: OpenAPI URL, OAuth discovery, scopes, MCP endpoints, CLI packages, webhooks and self-serve onboarding.

Inferred read-only
infaris_list_products

List Infaris products with a one-line description and canonical URL.

Inferred read-only
infaris_get_when_to_use

Explain when an agent should use Infaris versus the Guard MCP/API/CLI, and how to authenticate with scoped OAuth permissions.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.infaris]
url = "https://infaris.com/.well-known/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "infaris": {
      "type": "http",
      "url": "https://infaris.com/.well-known/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: infaris
Remote MCP URL: https://infaris.com/.well-known/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "infaris": {
      "url": "https://infaris.com/.well-known/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code 
{
  "servers": {
    "infaris": {
      "type": "http",
      "url": "https://infaris.com/.well-known/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "infaris",
  "transport": "streamable-http",
  "url": "https://infaris.com/.well-known/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 2

https://infaris.com/mcp

No auth detected

MCP server metadata

Name
infaris
Version
1.0.0
Capabilities
toolsresources
Server instructions

Infaris public MCP server. Use it to learn what Infaris is, when to reach for Guard, and where OpenAPI, OAuth, the Guard MCP server, and the CLI live. It is read-only and needs no authentication. When to use: identity discovery, product orientation, developer-resource lookup. When not to use: live uptime data, creating monitors, or mutating a tenant. Those jobs belong on https://api.ipulse.one/mcp with read/write OAuth scopes, or the Guard CLI. Handshake: GET https://infaris.com/.well-known/mcp. JSON-RPC: POST https://infaris.com/.well-known/mcp or POST https://infaris.com/mcp.

Known tools 4

infaris_get_overview

Return a short overview of Infaris and its monitoring product Guard, with links to OpenAPI, MCP and docs.

Inferred read-only
infaris_get_developer_docs

Return Infaris developer resources: OpenAPI URL, OAuth discovery, scopes, MCP endpoints, CLI packages, webhooks and self-serve onboarding.

Inferred read-only
infaris_list_products

List Infaris products with a one-line description and canonical URL.

Inferred read-only
infaris_get_when_to_use

Explain when an agent should use Infaris versus the Guard MCP/API/CLI, and how to authenticate with scoped OAuth permissions.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.infaris]
url = "https://infaris.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "infaris": {
      "type": "http",
      "url": "https://infaris.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: infaris
Remote MCP URL: https://infaris.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "infaris": {
      "url": "https://infaris.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code 
{
  "servers": {
    "infaris": {
      "type": "http",
      "url": "https://infaris.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "infaris",
  "transport": "streamable-http",
  "url": "https://infaris.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.