mcpbeat Sign in

Wodan Posture MCP Server

by goedvps-app-wodan-posture Your server? Claim it
not responding

Wodan Posture is listed as active in the registry but did not answer our last check. It exposes 11 tools.

Access-posture reports for agent data sourcing: robots, bot wall, licensing. Paid per call via x402.

Uptime history 48 days of history · worst day 0%
48 days agonow
0.0%
Uptime 24h
0 of 92 checks
11
Tools
read from the server
153 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 15

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 25 September 2026. No other catalogue keeps this.

1 Oct a tool appeared origin_policy
30 Sep 2 tools appeared can_fetch, crawl_policy
30 Sep a tool description was rewritten robots_check
29 Sep a tool appeared domain_report
28 Sep a tool appeared page_report
27 Sep 3 tools appeared page_data, pages_posture, robots_check
26 Sep 3 tools changed the parameters they ask for page_posture, page_sources, posture_preview
26 Sep a tool appeared page_sources
25 Sep 2 tool descriptions were rewritten page_posture, posture_preview

Wodan Posture does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add wodan-posture --transport http https://wodan-posture.app.goedvps.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://wodan-posture.app.goedvps.com/mcp
~/.codex/config.toml
[mcp_servers.wodan-posture]
url = "https://wodan-posture.app.goedvps.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "wodan-posture": {
      "url": "https://wodan-posture.app.goedvps.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "wodan-posture": {
      "type": "http",
      "url": "https://wodan-posture.app.goedvps.com/mcp"
    }
  }
}

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

page
page_data
Paid: $0.03 USDC on Base per call. No signup, no API key. Returns the machine-readable data one public http(s) URL already publishes: every JSON-LD block, OpenGraph/Twitter-card/standard meta, embedded JSON state blobs (e.g. __NEXT_DATA__), parsed entries if the document is RSS/Atom/JSON Feed, HTML tables, and alternate/canonical links - each capped and returned exactly as observed, nothing invented or inferred by a model. Does not render JavaScript, does not follow links off the page, does not summarize. An unanalysable URL is never charged for (error target_not_analysable); a page with nothing extractable answers nothing_to_report, also uncharged.
page_posture
Paid: $0.01 USDC on Base per call, paid automatically by an x402-capable MCP client. No signup, no API key. Analyses one public http(s) URL and reports whether an agent may treat it as a machine-readable data source: exact-path robots.txt verdict, bot-wall vendor, JavaScript requirement, extractable content, JSON-LD types, licence hint, evidence lines. Verdicts: open, machine_readable, robots_disallowed, bot_walled, auth_required, js_rendered, thin_content, unreachable. An unanalysable URL is never charged for (error target_not_analysable). Argument: url. Free alternative for the verdict alone: posture_preview.
page_report
Paid: $0.04 USDC on Base per call. No signup, no API key. The whole-page report for one public http(s) URL in ONE payment: the access-posture report (page_posture), where the data is (page_sources) and the data itself (page_data), composed from the same builders as the three single routes, so $0.04 instead of $0.06 for three separate calls. If the posture component cannot be produced the whole call fails closed (target_not_analysable) and nothing settles; if sources or data fails or times out the answer is still 200 with that component absent from `products` and named in `partial`.
page_sources
Paid: $0.02 USDC on Base per call, paid automatically by an x402-capable MCP client. No signup, no API key. For one public http(s) URL returns the posture verdict plus where the data is: sitemaps (robots.txt Sitemap lines and /sitemap.xml, with the status observed), RSS/Atom feeds, whether /llms.txt answers 200, the status of /.well-known/x402, ai-plugin.json and mcp.json, JSON/CSV/XML endpoints, JSON-LD types, licence hint. Every field is observed or explicitly empty with a reason. An unanalysable URL (target_not_analysable) or a site that advertises nothing (nothing_to_report) is never charged for. Argument: url.
can
can_fetch
Paid: $0.02 USDC on Base per call, paid automatically by an x402-capable MCP client. No signup, no API key. Answers the RFC 9309 crawl-permission question for up to 100 public http(s) URLs in one payment: may the given crawler agent fetch each URL? One robots.txt fetch per distinct origin (at most 25 origins), not one per URL. Argument agent is the crawler token (e.g. 'GPTBot'); optional, defaults to the wildcard '*' group. An unreadable or unparsable robots.txt is reported as status unknown, allowed null - never guessed as allowed. Errors are never charged for. The free tool robots_check answers the same question for one URL at a time, for nothing. Arguments: urls (1 to 100 strings), agent (optional).
crawl
crawl_policy
Free, no signup: shares posture_preview's 60-calls-per-hour budget across all callers. Returns live RFC 9309 allow/disallow decisions for a fixed, versioned sample of up to 24 public origins, computed from each origin's own robots.txt. A robots.txt that cannot be read is reported as unknown, never as allowed. Argument: limit (optional, 1-24, default all origins in the seed). The HTTP equivalent is GET /v1/agents/policy (add ?format=csv for CSV). For a single page's full access-posture report, use the paid tool page_posture ($0.01).
domain
domain_report
Paid: $0.06 USDC on Base per call. No signup, no API key. The domain-level agent-access report for the ORIGIN of one public http(s) URL: robots.txt decisions for every well-known agent token at the given path, which agent-facing documents the origin publishes (llms.txt, /.well-known/x402, /.well-known/mcp.json, security.txt), whether its declared sitemap actually contains pages the origin allows an agent to fetch, and a sample of those pages analysed for agreement with the robots policy. Verdicts: open, restricted, blocked, mixed, unreachable. Answers a different question than page_posture: not 'can I fetch this one page' but 'what is this whole site's policy toward agents'. Free companion for a single agent at a single path: robots_check. An unanalysable target is never charged for (target_not_analysable); an origin that publishes nothing at all (no robots.txt, no discovery document, no sitemap, unreachable root page) answers nothing_to_report, also uncharged.
origin
origin_policy
Paid: $0.03 USDC on Base per call, paid automatically by an x402-capable MCP client. No signup, no API key. Returns the whole crawl policy of one public http(s) URL's origin, from ONE robots.txt fetch: every group, every rule with its line number in the file, which group governs each well-known agent and why, sitemaps resolved to absolute URLs, and two digests (robots_txt_sha256, policy_hash) to watch a policy for changes with one cheap call. An unanalysable URL is never charged for (error target_not_analysable). The free tool robots_check answers one agent's allow/disallow decision for one URL, for nothing. Argument: url.
pages
pages_posture
Paid: $0.05 USDC on Base per call, as GET /v1/pages/posture?url=...&url=... (repeat url up to ten times) or POST /v1/pages/posture with a JSON body. No signup, no API key. Analyses up to 10 public http(s) URLs in ONE payment and ONE settlement, instead of paying page_posture ten times: the same access-posture report as page_posture, per URL, as a verdict array. An individual unanalysable or empty URL is never a batch failure - it is reported as its own error entry in results, target_not_analysable or nothing_to_report - and the batch is only charged (settles) when at least one URL could be analysed; if every URL fails the whole call answers 404 and nothing settles. Free companions cover a single URL: posture_preview and robots_check.
posture
posture_preview
Free, no payment and no signup: 60 calls per hour, shared across all callers. Returns the headline of the same analysis - verdict, confidence, the full report's field schema, one evidence line and the price - so a caller can decide before paying. Use it when you only need the verdict; call page_posture ($0.01) for the complete report with evidence and provenance.
robots
robots_check
Free, no signup: shares posture_preview's 60-calls-per-hour budget across all callers. Answers the RFC 9309 question for one public http(s) URL and one crawler token (argument agent, e.g. 'GPTBot'; optional, defaults to the wildcard '*' group): may this agent fetch this URL? Also reports the same decision for '*', gptbot, claudebot, googlebot, perplexitybot and ccbot in one call. An unreachable or unparsable robots.txt is reported as status unknown with allowed null - never guessed as allowed. The HTTP equivalent is GET /v1/robots/check. For the wider questions this tool does not answer: page_posture ($0.01) is the full access-posture report, page_sources ($0.02) is where the data is, page_data ($0.03) is the data itself. For many URLs at once, can_fetch ($0.02) answers the same question for up to 100 URLs in one payment, one robots.txt fetch per distinct origin.

Endpoints

URLTransportStateLatencyChecked
https://wodan-posture.app.goedvps.com/mcp streamable-http answering 153 ms 1 min ago

Alternatives to Wodan Posture

same job, measured the same way
Crypto Market Data
by zaffy18

Live crypto market data and Hyperliquid wallet reports for AI agents, paid per call with x402.

154 installs/wk 15 tools answering
Magneta Contract Risk
by bosacks

Smart-contract risk reports for AI agents on 20 EVM chains, paid per call via x402 ($0.02 USDC).

4 tools answering
systemprompt.io reports
by systemprompt

Paid EU AI Act compliance reports for agents. $1.50 per call via x402 (USDC on Base) or Stripe.

2 tools answering
Ruff Lint X402
by divine-software-creations

Ruff Python linting for AI agents, pay-per-call via x402 ($0.005 USDC on Base).

94 installs/wk local only
AgentReady (Base wallet readiness)
by madebydevx-agentready

Agent-readiness score for a Base wallet: gas, USDC float, activity. Paid x402 report.

2 tools answering
agent-site-audit - website audits for agents
by audito

Paid website audits for agents: flat JSON, HTML report, deep audit. USDC via x402.

4 tools answering
NSW Planning Data (x402)
by zuo305

NSW DAs, CDCs and property planning reports: zoning, height, FSR, nearby DAs. Pay per call via x402.

12 tools answering
Verdoc
by verdochello

Deterministic AGENTS.md and repo analysis for coding agents, paid per call in USDC over x402.

local only

Wodan Posture — questions

Answers built from our own checks of this server.

What can Wodan Posture do?
It exposes 11 tools, read directly from the server on our last check. Among them: can_fetch, crawl_policy, domain_report, origin_policy, page_data, page_posture and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Wodan Posture working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 153 ms. The bar chart above shows every period we have measured.
The registry lists Wodan Posture as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Wodan Posture?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Wodan Posture need an API key?
No. Wodan Posture completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.