Contact Affordance

org.ottobotPublished by ottobot.orgv0.1.1Updated Oct 24, 2026

Check how to contact a business website, and whether that contact path actually works.

The publisher's own server: QR Rápido

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

A remote MCP server that checks a business website's contact path and reports whether a human can actually reach it.

What you can do
Check a business website's contact path from a given URL and get a verdict of reachable or inconclusive, plus the forms found with their resolved handler URLs and any published phone or email. It never submits anything, so it only inspects what is publicly offered.
When to use it
Useful when you want to verify how to reach a business before outreach, or to confirm that a listed contact form or address actually works rather than trusting a page at face value.
Requirements
A remote streamable HTTP endpoint; no package, account, API key, environment variable or header is declared. The assistant needs network access to the endpoint, and the endpoint itself must be able to fetch the target website.
Before you install
It fetches third-party websites, so the target URL is sent to the remote service. It only reads pages and never submits forms, but results can be inconclusive, so treat a verdict as a signal rather than proof.

Installation

In SourceWeft

  1. Open Contact Affordance in the dashboard and add it to a workspace.
  2. 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/org.ottobot%2Fcontact-affordance/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": {
    "contact-affordance": {
      "type": "http",
      "url": "https://contact-affordance-mcp.ottobot2025.workers.dev/mcp"
    }
  }
}

README

MCP Registry

The MCP registry provides MCP clients with a list of MCP servers, like an app store for MCP servers.

📤 Publish my MCP server | ⚡️ Live API docs | 👀 Ecosystem vision | 📖 Full documentation

Development Status

2025-10-24 update: The Registry API has entered an API freeze (v0.1) 🎉. For the next month or more, the API will remain stable with no breaking changes, allowing integrators to confidently implement support. This freeze applies to v0.1 while development continues on v0. We'll use this period to validate the API in real-world integrations and gather feedback to shape v1 for general availability. Thank you to everyone for your contributions and patience—your involvement has been key to getting us here!

2025-09-08 update: The registry has launched in preview 🎉 (announcement blog post). While the system is now more stable, this is still a preview release and breaking changes or data resets may occur. A general availability (GA) release will follow later. We'd love your feedback in GitHub discussions or in the #registry-dev Discord (joining details here).

Registry Working Group:

Contributing

We use multiple channels for collaboration - see modelcontextprotocol.io/community/communication.

Often (but not always) ideas flow through this pipeline:

  • Discord - Real-time community discussions
  • Discussions - Propose and discuss product/technical requirements
  • Issues - Track well-scoped technical work
  • Pull Requests - Contribute work towards issues

Quick start:

Pre-requisites
  • Docker
  • Go - version per the go directive in go.mod; the Go toolchain fetches it for you
  • ko - Container image builder for Go (installation instructions)
  • golangci-lint - version per the golangci-lint-action pin in ci.yml, so local lint matches CI
Running the server
bash
# Start full development environmentmake dev-compose

This starts the registry at localhost:8080 with PostgreSQL. The database uses ephemeral storage and is reset each time you restart the containers, ensuring a clean state for development and testing.

Note: The registry uses ko to build container images. The make dev-compose command automatically builds the registry image with ko and loads it into your local Docker daemon before starting the services.

By default, the registry seeds from the production API with a filtered subset of servers (to keep startup fast). This ensures your local environment mirrors production behavior and all seed data passes validation. For offline development you can seed from a file without validation with MCP_REGISTRY_SEED_FROM=data/seed.json MCP_REGISTRY_ENABLE_REGISTRY_VALIDATION=false make dev-compose.

The setup can be configured with environment variables in docker-compose.yml - see .env.example for a reference.

Alternative: Running a pre-built Docker image

Pre-built Docker images are automatically published to GitHub Container Registry. Note that the image does not bundle PostgreSQL, so you need to run your own and point the registry at it via MCP_REGISTRY_DATABASE_URL (see docker-compose.yml for a working example):

bash
# Run latest stable releasedocker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:latest
# Run latest from main branch (continuous deployment)docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main
# Run specific release versiondocker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:v1.0.0
# Run development build from main branchdocker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main-20250906-abc123d

Available tags:

  • Releases: latest, v1.0.0, v1.1.0, etc.
  • Continuous: main (latest main branch build)
  • Development: main-<date>-<sha> (specific commit builds)
Publishing a server

Publishing an MCP server does not happen through a pull request to this repository. Adding a server.json, a server directory, or an entry in data/seed.json will not publish or list your server, even if the PR is merged. Use the mcp-publisher CLI from your server's own project instead.

To publish a server, we've built a simple CLI. You can use it with:

bash
# Build the latest CLImake publisher
# Use it!./bin/mcp-publisher --help

See the publisher guide for more details.

Other commands
bash
# Run lint, schema validation, and all tests# Note: this also runs `make dev-down`, stopping any running dev-compose environmentmake check

There are also a few more helpful commands for development. Run make help to learn more, or look in Makefile.

Architecture

Project Structure

├── cmd/                     # Application entry points│   ├── publisher/           # Server publishing tool│   └── registry/            # Registry API server├── data/                    # Seed data├── deploy/                  # Deployment configuration (Pulumi)├── docs/                    # Documentation├── internal/                # Private application code│   ├── api/                 # HTTP handlers and routing│   ├── auth/                # Authentication (GitHub OAuth, JWT, namespace blocking)│   ├── config/              # Configuration management│   ├── database/            # Data persistence (PostgreSQL)│   ├── importer/            # Seed data import│   ├── service/             # Business logic│   ├── telemetry/           # Metrics and monitoring│   └── validators/          # Input validation├── pkg/                     # Public packages│   ├── api/                 # API types and structures│   │   └── v0/              # Version 0 API types│   └── model/               # Data models for server.json├── scripts/                 # Development and testing scripts├── tests/                   # Integration tests└── tools/                   # CLI tools and utilities    └── validate-*.sh        # Schema validation tools

Authentication

Publishing supports multiple authentication methods:

  • GitHub OAuth - For publishing by logging into GitHub
  • GitHub OIDC - For publishing from GitHub Actions
  • DNS verification - For proving ownership of a domain and its subdomains
  • HTTP verification - For proving ownership of a domain

The registry validates namespace ownership when publishing. E.g. to publish...:

  • io.github.domdomegg/my-cool-mcp you must login to GitHub as domdomegg, or be in a GitHub Action on domdomegg's repos
  • me.adamjones/my-cool-mcp you must prove ownership of adamjones.me via DNS or HTTP challenge

Community Projects

Check out community projects to explore notable registry-related work created by the community.

More documentation

See the documentation for more details if your question has not been answered here!

Source: README.md at commit 11b7b0e

Tools

1

check_contact_path

Given a business website URL, report how a human is meant to make contact and whether that path is actually reachable. Returns a verdict of 'reachable' or 'inconclusive', the forms found with their resolved handler URLs, and any published phone or email. Never submits anything. Answers 'inconclusive' rather than guessing when a site is client-rendered, bot-protected or parked -- about 64% of real sites cannot be judged from outside, and a confident wrong answer is worse than an honest one.

Parametersurlrequired

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

90% 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Qrrapido integrations

QR Rápido

site.qrrapidoOfficial publisher

A remote MCP server that lets an assistant generate QR codes for URLs, PIX payments, Wi-Fi, vCards, WhatsApp and similar targets.

Streamable HTTPWeb executableAuth
Media & DesignCredential requiredOct 24, 2026

MCP Registry Server

ai.com.mcpOfficial publisher

A remote MCP registry server that lets an assistant browse registered MCP servers, their versions, and version details.

Streamable HTTPWeb executable
Knowledge & Memory3 toolsOct 24, 2026

Domain Liveness

org.ottobot

Remote MCP server that checks whether a business's website is still live, testing apex and www domains with separate DNS and HTTP lookups.

Streamable HTTPWeb executable
Web Search & Scraping1 toolOct 27, 2026