Dechonet-MCP

My IP Info

ip_info

Read-onlyIdempotent

Report information about the caller's own public IP as seen by the server: IPv4/IPv6 address, ISP, ASN, approximate geolocation, and proxy/VPN heuristics. Takes no input — it reflects the egress IP of THIS MCP server's network, which is usually NOT the end user's IP. Use this to discover the server's outbound IP or test connectivity. To inspect a specific, known IP instead, use asn_lookup or reverse_dns. Read-only; requires no API key; rate-limited.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`kpis`	No	Key metrics as label/value pairs
`grade`	No	Letter grade (A+ to F) when the tool grades the target
`score`	No	0-100 score when the tool scores the target
`issues`	No	Detected problems, severity-rated
`status`	Yes	Overall verdict, e.g. 'good' \| 'warning' \| 'bad' \| 'info' \| 'unknown'
`actions`	No	Recommended next actions, most important first
`summary`	No	One-paragraph interpretation of the result
`receipts`	No	Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature.
`reportUrl`	Yes	Human-facing interactive report for this exact lookup on dechonet.com
`observation`	No	How much was actually observed and when. A partial observation means some checks did not answer: missing parts are not verified, never clean.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

addedOutput schema / properties / receipts

Added value: +{
+  "description": "Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature.",
+  "items": {
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "tool": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "tool",
+      "id",
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedOct 15, 2026

addedOutput schema / properties / observation

Added value: +{
+  "description": "How much was actually observed and when. A partial observation means some checks did not answer: missing parts are not verified, never clean.",
+  "properties": {
+    "ageMinutes": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "cached": {
+      "type": "boolean"
+    },
+    "observedAt": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "state": {
+      "enum": [
+        "complete",
+        "partial",
+        "unknown"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedSep 2, 2026

TDQS

A4.7/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover read-only/idempotent/non-destructive. The description adds important context beyond annotations: no input, reflects the MCP server's egress IP rather than the user's, requires no API key, and is rate-limited. It does not detail the rate-limit cadence or exact geolocation accuracy, but it covers much more than the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the purpose, then the key caveat about egress IP, then the alternative routing. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-param, read-only introspection tool with an output schema, the description is complete. It clarifies the semantic caveat (server vs user IP), which is the main risk of misinterpretation, and points to alternatives. Output details are covered by the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Takes zero parameters, so the baseline is 4. The description clarifies that there is no input and explains the implicit input is the server's network, which is useful even though no parameters exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Report information about the caller's own public IP') and enumerates the fields returned (IPv4/IPv6, ISP, ASN, geolocation, proxy/VPN heuristics). It also explicitly distinguishes itself from siblings asn_lookup and reverse_dns regarding known IPs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use ('discover the server's outbound IP or test connectivity') and when not to ('To inspect a specific, known IP instead, use asn_lookup or reverse_dns'). This is about as clear as it gets.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Dechonet-MCP tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?