ServerCard Trust MCP

space.servercardtrustPublished by servercardtrust.spaceOfficial publisherv0.1.0Updated Oct 24, 2026

Paid remote MCP for server-card validation, auth checks, trust packets, and readiness.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Paid remote MCP server that lets an assistant validate server cards, check auth, produce trust packets and assess readiness.

What you can do
Validate server cards and check their authentication setup through a remote MCP endpoint. Generate trust packets that summarize a server's trust posture. Assess readiness of a server card before publication or use. Access is gated by a bearer token obtained after checkout and token claim.
When to use it
Useful when you publish or review MCP server cards and want an assistant to check validity, authentication and readiness, or to assemble a trust packet for review.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package. A paid checkout is required, followed by claiming an MCP token, which is sent as the Authorization bearer header.
Before you install
This is a paid service: obtaining the token involves a checkout and possibly spending money. The Authorization bearer token is a secret and should be kept out of logs and shared transcripts. The tool list is not published, so confirm what it writes or sends before relying on it.

Installation

In SourceWeft

  1. Open ServerCard Trust MCP in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/space.servercardtrust%2Fservercardtrust-mcp/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.

{
  "mcpServers": {
    "servercard-trust": {
      "type": "http",
      "url": "https://servercardtrust.space/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.0LatestSep 16, 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.