WebMCP Eval

com.webmcp-evalPublished by webmcp-eval.comOfficial publisherv1.0.0Updated Oct 27, 2026

Evaluate one public URL for WebMCP readiness: intent, tools observed, recommended, do-not-expose.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Remote MCP endpoint that evaluates a single public URL for WebMCP readiness, reporting intent, tools observed, and recommended or do-not-expose items.

What you can do
  • Evaluate one public URL for WebMCP readiness.
  • Report the page's intent and the tools observed on it.
  • Return recommended items and a do-not-expose list for that page.
When to use it
Useful when you want a quick readiness check of a public web page before exposing its capabilities to an assistant, or when comparing pages for WebMCP suitability.
Requirements
A remote streamable HTTP endpoint; no local install. Authentication is required: an OAuth flow or an Authorization header carrying a Bearer API key obtained from the provider's site checkout. Network access to the endpoint is needed.
Before you install
Access requires a paid-looking API key from the provider's checkout, so expect account and billing implications. The Authorization header carries a live secret that should not be shared or logged. Only public URLs should be submitted, since the page address is sent to a third-party service.

Installation

In SourceWeft

  1. Open WebMCP Eval in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.webmcp-eval%2Fwebmcp-eval/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "webmcp-eval": {
      "type": "http",
      "url": "https://mcp.webmcp-eval.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 18, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.