Connect to Machine Presence Inspector
Inspect public website signals through MCP. The human Inspector and machine interface use the same inspection engine and normalized result contract.
Connection
Use a client that supports MCP Streamable HTTP with protocol 2025-11-25.
Endpoint: https://mcp.onthestacks.dev/mcp
Tool: inspect_machine_presence
Authentication: no account or API key required.
Input
Supply one public HTTP or HTTPS URL:
{"url":"https://example.com/"}The client initializes the connection, discovers tools, then calls inspect_machine_presence. Example JSON-RPC tool invocation after initialization:
{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"inspect_machine_presence","arguments":{"url":"https://example.com/"}}}POST UTF-8 JSON with Content-Type: application/json, Accept: application/json, text/event-stream, and, after initialization, MCP-Protocol-Version: 2025-11-25. Initialization uses the supported version, your clientInfo, and capabilities; send notifications/initialized before tool discovery. Responses use JSON. This stateless profile requires no session identifier and provides no persistent event stream.
Results and limitations
Successful calls return structuredContent and an equivalent JSON text representation. Results include the requested and final URLs, check time, inspection version, outcome, observations, source evidence, and limitations across Access, Identity, Structure, Policy, Interfaces, and Actionability.
Observation statuses are PRESENT, ABSENT, CONFLICTING, INACCESSIBLE, and UNKNOWN. A partial result is useful evidence with stated limitations. An unverified condition remains unknown. Results describe the public resources observed at inspection time, not a certification or guarantee.
Inspection is read-only. It does not sign in, run site JavaScript, send cookies, or submit forms to inspected sites. Only public HTTP and HTTPS resources are eligible. Robots directives and bounded request limits can prevent a complete inspection.
Errors and fair use
Invalid requests may return an HTTP or JSON-RPC error. A failed inspection call returns a tool result with isError: true and a safe error code/message. Public traffic shares bounded capacity and rate limits; respect HTTP 429, Retry-After when supplied, and any rate-limit or busy tool error. Retry after a delay rather than issuing parallel retries. Clients should allow up to 45 seconds for a response.
Privacy and version
No inspection history is stored by the application. Routine logs exclude inspected URLs, request bodies, and full results. The infrastructure providers process connection metadata to deliver and protect the service. Save evidence in your own client only when needed.
Inspector version 0.1.0; result schema 1.0.0; MCP protocol 2025-11-25. Support for this profile does not imply support for every client or newer protocol revision.