MCP security checks — WARDEN and HISTOR

{
  "mcpServers": {
    "dev.modelmarket/mcp-security": {
      "url": "https://modelmarket.dev/tools/mcp/security"
    }
  }
}

Indexed tools

Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.

4 shown · authentication unknown

• Server history (HISTOR)

  histor_check

  Look up an MCP server in HISTOR, a public append-only log of MCP tool sets: when its tool set was first pinned, how often it changed, and what the pattern scan found. HISTOR answers from its own observations and never contacts the server.

  Schema valid · SHA-256 444dd23923d2…

  View input schema

  {
    "type": "object",
    "properties": {
      "endpoint": {
        "type": "string",
        "description": "https URL of the MCP server"
      },
      "name": {
        "type": "string",
        "description": "Or its registry name, e.g. io.github.owner/server"
      }
    }
  }

• Tool list token cost

  tool_list_cost

  How many tokens an MCP server's tool list adds to every model request, what that costs per 1,000 requests, the heaviest tools, and where it sits among 18,204 packages and 16,170 remote servers. Send a tools/list or name a server HISTOR observes.

  Schema valid · SHA-256 7f3be67c89d3…

  View input schema

  {
    "type": "object",
    "properties": {
      "tools": {
        "type": "array",
        "items": {
          "type": "object"
        },
        "description": "A tools/list result"
      },
      "server": {
        "type": "string",
        "description": "Or a server HISTOR observes: https endpoint, npm:<package>, pypi:<package> or registry name"
      }
    }
  }

• Scan tool definitions (WARDEN)