Dechonet MCP

My IP Info

ip_info

Read-onlyIdempotent

Retrieve the server's public IP, ISP, ASN, approximate geolocation, and proxy/VPN status. No input needed; useful for verifying outbound network identity.

Instructions

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

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON 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
`reportUrl`	Yes	Human-facing interactive report for this exact lookup on dechonet.com

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.1.0Sep 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "actions": {
+      "description": "Recommended next actions, most important first",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "grade": {
+      "description": "Letter grade (A+ to F) when the tool grades the target",
+      "type": "string"
+    },
+    "issues": {
+      "description": "Detected problems, severity-rated",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "key": {
+            "type": "string"
+          },
+          "severity": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "severity",
+          "key"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "kpis": {
+      "description": "Key metrics as label/value pairs",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "label": {
+            "type": "string"
+          },
+          "value": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "label",
+          "value"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "reportUrl": {
+      "description": "Human-facing interactive report for this exact lookup on dechonet.com",
+      "type": "string"
+    },
+    "score": {
+      "description": "0-100 score when the tool scores the target",
+      "type": "number"
+    },
+    "status": {
+      "description": "Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown'",
+      "type": "string"
+    },
+    "summary": {
+      "description": "One-paragraph interpretation of the result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "reportUrl"
+  ],
+  "type": "object"
+}

First observedv0.1.0Jun 17, 2026

TDQS

A5/5.0

Behavior5/5

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

Description aligns with annotations (readOnlyHint, idempotentHint, destructiveHint false) and adds useful behavioral context: takes no input, reflects egress IP, read-only, no API key required, rate-limited. No contradictions with 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?

Description is compact, front-loaded with the primary purpose, and contains no redundant or filler wording. All sentences add value.

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?

Despite having no parameters, the description fully covers what the tool does, what data it returns, and its constraints. The listed return fields give enough context for an agent to decide whether this tool fits the task.

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

Parameters5/5

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

Tool has zero parameters and the schema reflects this. Description explicitly reinforces 'Takes no input', leaving no ambiguity about invocation requirements.

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?

Description clearly identifies the resource (caller's own public IP as seen by server) and the action (report), and enumerates the data returned (IPv4/IPv6, ISP, ASN, geolocation, proxy/VPN heuristics). It also distinguishes itself from related sibling tools by noting asn_lookup/reverse_dns are for specific 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 states when to use this tool (discover server outbound IP or test connectivity) and when to use alternatives (specific known IP -> asn_lookup or reverse_dns). This is clear usage guidance.

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

Deploy Server