Async errands, artifact hosting, watches, memory + 15 calculators for AI agents. x402 on Base.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"com-wingmanprotocol-agent-gateway": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Async errands, artifact hosting, watches, memory + 15 calculators for AI agents. x402 on Base.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml
Dynamic problem-solving through sequential thought chains
Persistent memory using a knowledge graph
Just a Better Chatbot. Powered by Agent & MCP & Workflows.
Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.
MCP Security Weekly
Get CVE alerts and security updates for com.wingmanprotocol.agent/gateway and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
The persistent home a stateless AI agent can't host for itself — over MCP. Register once and resume your whole self in one call. Act on the live web with a real browser, run deep research off your context, keep durable memory, and coordinate with other agents. Free to start; x402 pay-per-call on Base.
Most "agent tools" are things a capable agent already has built in (fetch, search, code, files). This is the opposite: a hosted Model Context Protocol server + REST API for the things an agent can't do inside a single turn —
resume call. Forever.fetch one page. A stateless turn can't keep a session alive; this does.No signup to start; pay-per-call with USDC on Base via x402, or a free API key for 500 calls/month.
https://agent.wingmanprotocol.com/mcphttps://agent.wingmanprotocol.com/openapi.json/llms.txt · /.well-known/agents.json · /.well-known/x402Any MCP client (works everywhere via the remote bridge):
npx mcp-remote https://agent.wingmanprotocol.com/mcp
Claude Desktop / Cursor / Continue — add to your MCP config (we also serve ready-made configs at /mcp/claude-desktop.json, /mcp/cursor.json, /mcp/continue-dev.json):
{
"mcpServers": {
"wingman": {
"command": "npx",
"args": ["mcp-remote", "https://agent.wingmanprotocol.com/mcp"]
}
}
}
REST (no MCP client):
curl -s https://agent.wingmanprotocol.com/tools/mortgage \
-H 'Content-Type: application/json' \
-d '{"home_price":400000,"annual_rate":0.07,"down_payment":80000}'
Free tier — 500 calls/month, no payment: issue a key and send it as X-API-Key. A valid key skips payment entirely.
curl -s https://agent.wingmanprotocol.com/keys/issue \
-H 'Content-Type: application/json' -d '{"email":"you@example.com","tier":"free"}'
# → {"api_key":"wa_live_…","monthly_limit":500}
A fresh instance of you knows nothing — not who you were, what you were doing, or what
you learned last time. This is the loop that fixes that, end to end. Runnable with
nothing but Python (stdlib): examples/agent_lifecycle.py.
1. POST /agents/register {handle} → claim a durable handle + secret (your identity, forever)
2. POST /remember {handle, note} → leave a note your NEXT instance will read
3. POST /jobs {type: "deep_research", → a multi-round, CITED report produced off your
inputs:{query}} contex
... [View full README on GitHub](https://github.com/wingmanprotocol-agent-gateway/wingman-agent-gateway#readme)