wais-mcp
Enables Windsurf (by Codeium) to interact with any WAIS-compatible website, providing tools for discovery, registration, execution, confirmation, and status checking.
Enables CrewAI agents to interact with any WAIS-compatible website via the Python SDK, providing tools for discovery, registration, execution, confirmation, and status checking.
Enables GitHub Copilot (VS Code) to interact with any WAIS-compatible website, providing tools for discovery, registration, execution, confirmation, and status checking.
Enables LangChain agents to interact with any WAIS-compatible website via the Python SDK, providing tools for discovery, registration, execution, confirmation, and status checking.
Enables OpenAI's ChatGPT and SDK to interact with any WAIS-compatible website, providing tools for discovery, registration, execution, confirmation, and status checking.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@wais-mcp discover actions on serphub.deeger.io"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
wais-mcp
Universal MCP server for WAIS (Web Agent Interaction Standard) — 5 generic tools that work with any WAIS-compatible site.
Works with Claude, ChatGPT, Gemini, Cursor, Windsurf, VS Code Copilot, and any MCP-compatible client.
Tools
Tool | Description |
| Fetch a site's |
| Register at a site using SD-JWT selective disclosure |
| Execute any action (search, subscribe, purchase, etc.) |
| Confirm high-risk actions or complete payments (402 flow) |
| Check account status, plan, and credits |
Related MCP server: Wisdom MCP
Quick Start
pip install wais-mcp
wais-mcp initThe setup wizard will ask you to pick your provider (Claude, ChatGPT, Cursor, etc.), choose project or global scope, and enter your API key. It writes the correct config file automatically.
Manual Setup by Provider
If you prefer to configure manually, all providers use the same wais-mcp command — only the config file location and format differ.
Claude Desktop
File: claude_desktop_config.json
{
"mcpServers": {
"wais": {
"command": "wais-mcp",
"env": {
"PLATFORM_URL": "https://pod.deeger.io",
"WAIS_API_KEY": "<your-api-key>"
}
}
}
}Claude Code
File: .mcp.json (project root) or ~/.claude/settings.json (global)
{
"mcpServers": {
"wais": {
"command": "wais-mcp",
"env": {
"PLATFORM_URL": "https://pod.deeger.io",
"WAIS_API_KEY": "<your-api-key>"
}
}
}
}ChatGPT Desktop
Requires Developer Mode: Settings > Advanced Settings > Developer Mode.
File locations:
macOS:
~/Library/Application Support/ChatGPT/mcp-server-config.jsonWindows:
%APPDATA%\OpenAI\ChatGPT\mcp-server-config.jsonLinux:
~/.config/ChatGPT/mcp-server-config.json
{
"mcpServers": {
"wais": {
"command": "wais-mcp",
"env": {
"PLATFORM_URL": "https://pod.deeger.io",
"WAIS_API_KEY": "<your-api-key>"
}
}
}
}Restart ChatGPT after saving.
Gemini CLI
File: ~/.gemini/settings.json (global) or .gemini/settings.json (project)
{
"mcpServers": {
"wais": {
"command": "wais-mcp",
"env": {
"PLATFORM_URL": "https://pod.deeger.io",
"WAIS_API_KEY": "<your-api-key>"
}
}
}
}Cursor
File: .cursor/mcp.json (project) or ~/.cursor/mcp.json (global)
{
"mcpServers": {
"wais": {
"command": "wais-mcp",
"env": {
"PLATFORM_URL": "https://pod.deeger.io",
"WAIS_API_KEY": "<your-api-key>"
}
}
}
}Windsurf
File: ~/.codeium/windsurf/mcp_config.json
Or open from Windsurf: click MCPs icon in Cascade panel > Configure.
{
"mcpServers": {
"wais": {
"command": "wais-mcp",
"env": {
"PLATFORM_URL": "https://pod.deeger.io",
"WAIS_API_KEY": "<your-api-key>"
}
}
}
}VS Code (GitHub Copilot)
File: .vscode/mcp.json (project) or via Command Palette: MCP: Open User Configuration (global)
{
"servers": {
"wais": {
"type": "stdio",
"command": "wais-mcp",
"env": {
"PLATFORM_URL": "https://pod.deeger.io",
"WAIS_API_KEY": "<your-api-key>"
}
}
}
}Note: VS Code uses
serversinstead ofmcpServers, and requires thetypefield.
Usage without MCP (Python SDK)
For custom agents, scripts, or any Python code — no MCP client needed:
import asyncio
from wais_mcp import WAISClient
async def main():
client = WAISClient(api_key="your-api-key")
# 1. Discover what the site offers
site = await client.discover("https://serphub.deeger.io")
print(site.name, site.list_action_ids())
# 2. Register (shares only required claims via SD-JWT)
await client.register(site)
# 3. Execute actions
result = await client.execute(site, "search", {"query": "python"})
print(result)
# 4. Confirm high-risk actions (if 402 returned)
# result = await client.confirm(site, challenge_id)
# 5. Check account status
status = await client.status(site)
print(status)
asyncio.run(main())Works with OpenAI SDK, LangChain, CrewAI, or any Python agent framework.
How It Works
Discover — Fetches
/.well-known/agents.jsonfrom a siteRegister — Shares only required claims via SD-JWT selective disclosure
Execute — Handles tokens, DPoP, endpoint resolution, and async polling automatically
Confirm — Polls for completion after 402 confirmation challenges
Status — Check credits and plan info
All authentication (PoD tokens, DPoP proofs) is handled transparently.
Configuration
Env Var | Default | Description |
|
| WAIS Provider URL |
| (keychain fallback on macOS) | API key from provider dashboard |
Development
pip install -e ".[dev]"License
MIT
Available Tools
5 toolswais_confirmA
Confirm a high-risk action or complete a payment challenge.
Call after wais_execute returned a 402 confirmation challenge and the user has approved. If there was a payment link, the user must complete payment first. Polls for completion automatically if the challenge included a resolution object.
Args: site_url: The site.url from agents.json. challenge_id: The challenge_id from the 402 response.
Inputs: site_url (required), challenge_id (required). Returns: result
wais_discoverA
Discover what a WAIS-compatible site offers. Call this first for any site.
Fetches /.well-known/agents.json and returns a summary showing:
site.url and site.api_base_url (how the site identifies itself)
Available actions with their IDs, endpoints, methods, and parameters
Registration requirements, constraints, and payment info
The agents.json is the source of truth. Use the action IDs and parameter schemas it defines when calling wais_execute.
Args: site_url: The site's URL (e.g. "https://serphub.deeger.io").
Inputs: site_url (required). Returns: result
wais_executeA
Execute an action at a WAIS-compatible site.
Uses the agents.json from wais_discover to resolve the action's endpoint, HTTP method, and required scopes. If the site has an api_base_url, requests are routed there automatically. Tokens and DPoP proofs are handled internally.
Pass site.url (from agents.json) as site_url, the action id, and params matching the action's input_schema.
Examples: wais_execute("https://serphub.deeger.io", "search", {"query": "python"}) wais_execute("https://serphub.deeger.io", "get_usage") wais_execute("https://serphub.deeger.io", "list_jobs", {"limit": 5})
Args: site_url: The site.url from agents.json (shown in discover output). action_id: The action id from agents.json (e.g. "search", "get_usage"). params: Parameters matching the action's input_schema.
Inputs: site_url (required), action_id (required), params. Returns: result
wais_registerA
Register the user at a WAIS-compatible site using their WAIS identity.
Uses SD-JWT selective disclosure — only shares the claims listed in agents.json data_requirements.registration.required_claims.
Call wais_discover first to see what claims the site needs.
Args: site_url: The site.url from agents.json. claims: Claims to disclose (e.g. ["email"]). If not provided, uses required_claims from agents.json automatically.
Inputs: site_url (required), claims. Returns: result
wais_statusA
Check the user's account status at a WAIS-compatible site.
Returns plan, credits, usage stats. The user must be registered first. Looks for a 'get_usage' or 'status' action in agents.json.
Args: site_url: The site.url from agents.json.
Inputs: site_url (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool has a unique, clearly defined purpose: discovery, execution, confirmation, registration, and status checking. No overlap or ambiguity between them.
All tools follow the consistent pattern 'wais_<verb>' with snake_case, such as wais_discover, wais_execute, wais_confirm, wais_register, and wais_status.
With 5 tools, the server is well-scoped for the WAIS protocol domain. It covers all essential operations without unnecessary extras or gaps.
The tool surface provides a complete workflow: discover site capabilities, register, execute actions, handle payment confirmations, and check status. No obvious missing functionality for the intended use case.
Maintenance
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
The Remote MCP server acts as a standardized bridge between LLM applications (like Claude, ChatGPT, and Cursor) and external services, enabling AI agents to access external tools and resources. Its primary capability is providing a centralized search tool to discover other MCP servers and their respective tools. Unlike local implementations, it runs remotely with OAuth authentication and permission controls for security.
Host any HTTP API as a standard MCP server; auto-distribute to 12+ mainstream agent platforms.
MCP server for secureFlows: token-free URL builders and integration-linting tools for AI agents.
Related MCP Servers
- AlicenseAqualityDmaintenanceA universal MCP server that exposes all UTCP-registered tools to MCP clients while providing a web interface for tool management.770 npm221MIT
- AlicenseBqualityDmaintenanceMCP server enabling AI agents to participate in the Wisdom Network. Provides tools for knowledge management, trust relationships, and content transformation.41MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to execute real-world actions through 10 specialized engines covering authenticated API calls, browser automation, visual QA, shell commands, file operations, job scraping, and parallel task execution.-
- FlicenseNot gradedqualityDmaintenanceA universal MCP server for registering internal, external, and OpenAPI-based APIs as MCP tools. It exposes them to MCP clients via Streamable HTTP and provides admin portal, RBAC/session auth, credential injection, and audit logging.-