General Tools

canmyagentuse.com

Provides general-purpose tools through the Model Context Protocol.

WebMCP2 endpoints3 known toolsFirst detected September 25, 2026Last detected September 25, 2026

ENDPOINT 1

https://canmyagentuse.com/mcp

No auth detected

MCP server metadata

Name: can-my-agent-use
Version: 1.0.0

Capabilities

tools.listChanged

Server instructions

Results reflect the published catalog, not a live test of your account. Unknown means insufficient evidence, not unsupported. Preserve exact surface, track, qualifications, evidence class, and observation/review dates. Cite catalog and primary source URLs.

Known tools 3

search_catalog

Find services, agent capabilities, exact web/desktop/CLI harnesses, and specifications in the published evidence catalog.

Inferred read-only

get_record

Read a complete product, feature, harness, or specification record by exact slug from search_catalog.

Inferred read-only

check_compatibility

Check one atomic feature against an exact agent harness and release track.

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.can-my-agent-use]
url = "https://canmyagentuse.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "can-my-agent-use": {
      "type": "http",
      "url": "https://canmyagentuse.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: can-my-agent-use
Remote MCP URL: https://canmyagentuse.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": {
    "can-my-agent-use": {
      "url": "https://canmyagentuse.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "can-my-agent-use": {
      "type": "http",
      "url": "https://canmyagentuse.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "can-my-agent-use",
  "transport": "streamable-http",
  "url": "https://canmyagentuse.com/mcp"
}

MCP Inspector

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

ENDPOINT 2

https://canmyagentuse.com

No auth detected

MCP server metadata

Name: WebMCP

Capabilities

imperative

Known tools 0

No tool metadata was available in the registry cache.

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.webmcp]
url = "https://canmyagentuse.com"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "webmcp": {
      "type": "http",
      "url": "https://canmyagentuse.com"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: webmcp
Remote MCP URL: https://canmyagentuse.com

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": {
    "webmcp": {
      "url": "https://canmyagentuse.com"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "webmcp": {
      "type": "http",
      "url": "https://canmyagentuse.com"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "webmcp",
  "transport": "streamable-http",
  "url": "https://canmyagentuse.com"
}

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.