Koskamo

AgentWares Readiness MCP

This MCP server allows AI agents to verify domain ownership and probe SaaS signup flows. It retrieves verification tokens, requests Playwright-based scans to test unassisted signup and API key minting, and polls for detailed scores and fix lists.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

AgentWares Readiness MCP logo, by AgentWaresCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-07Published by AgentWares
MCP endpoint (Streamable HTTP)
https://agentwares-readiness.vercel.app/api/mcp
Vendor documentation

What its tools do

3 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Can change data (1)

3 of 3 have a description · 3 of 3 declare behavior hints · 3 of 3 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Retrieve domain verification tokens for readiness scans
  • Request automated signup and API key minting probes
  • Poll scan status and retrieve detailed rubric scores

Source and maintenance

Community listingRegistry 0.1.2
Maintenance checked

Protocol and capabilities

Server
readiness-scorer 0.1.2
MCP protocol negotiated in check
2025-11-25
Tools
3 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  },
  "logging": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Scores whether an AI agent can sign up to a SaaS with no human: readiness_get_verification_token(url) → publish the token on the domain → readiness_request_scan(url) → readiness_get_scan(id). Only domains that proved ownership are probed. No key needed.

Tools

3 advertised

readiness_get_verification_token
Advertised by the server during the last successful anonymous check.
Advertised read-only

Step 1 of a readiness scan. Returns the domain-ownership token for the URL's host plus the three ways to publish it (DNS TXT record, <meta> tag, /.well-known file). The token is deterministic for the host, so calling this again returns the same value. Nothing is stored.

readiness_get_verification_token input schema
{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "format": "uri",
      "description": "Public https URL of the SaaS signup (or landing) page, e.g. https://example.com/signup"
    }
  },
  "additionalProperties": false
}
readiness_get_verification_token annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
readiness_request_scan
Advertised by the server during the last successful anonymous check.
Open-world

Step 2. Verifies domain ownership (DNS TXT / meta tag / .well-known must carry the token from readiness_get_verification_token), then queues a Playwright probe that tries to sign up, accept the terms and mint an API key with no human. Returns the scan id and the public results URL. Fails with DOMAIN_NOT_VERIFIED (with instructions) or RATE_LIMITED (3 scans per host per day). Never solves CAPTCHAs.

readiness_request_scan input schema
{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "format": "uri",
      "description": "Public https URL of the SaaS signup (or landing) page, e.g. https://example.com/signup"
    }
  },
  "additionalProperties": false
}
readiness_request_scan annotations
{
  "readOnlyHint": false,
  "openWorldHint": true,
  "idempotentHint": false,
  "destructiveHint": false
}
readiness_get_scan
Advertised by the server during the last successful anonymous check.
Advertised read-only

Step 3. Poll a scan by id. While status is queued/running only metadata is returned; when done you get the 0-100 score, grade, per-item rubric points with evidence, the fix list, and what could not be observed.

readiness_get_scan input schema
{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 64,
      "minLength": 8,
      "description": "scan id returned by readiness_request_scan"
    }
  },
  "additionalProperties": false
}
readiness_get_scan annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
622 ms
95th percentile latency
622 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 622 ms · metadata changed · 3 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http agentwares-readiness-mcp https://agentwares-readiness.vercel.app/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add agentwares-readiness-mcp --url https://agentwares-readiness.vercel.app/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable agentwares-readiness-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "agentwares-readiness-mcp": {
      "url": "https://agentwares-readiness.vercel.app/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "agentwares-readiness-mcp": {
      "type": "streamableHttp",
      "url": "https://agentwares-readiness.vercel.app/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start agentwares-readiness-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "agentwares-readiness-mcp": {
      "type": "http",
      "url": "https://agentwares-readiness.vercel.app/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http agentwares-readiness-mcp https://agentwares-readiness.vercel.app/api/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://agentwares-readiness.vercel.app/api/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "agentwares-readiness-mcp": {
      "serverUrl": "https://agentwares-readiness.vercel.app/api/mcp"
    }
  }
}

Let your agent find its tools

Find servers like AgentWares Readiness MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.