1NFER Inference Discovery

What 1NFER Inference Discovery MCP server does

The 1NFER Inference Discovery MCP server provides agent-facing access to information about 1NFER models, crypto funding terms, and task costs. Its discovery functions are intended for inspecting available catalogue aliases and understanding the cost or funding conditions before using an inference service. The supplied material does not identify individual discovery tool names, so clients should treat the available capabilities as the documented categories rather than assume a broader API.

The package also includes local-only account and invoice operations: register_account, account_status, create_invoice, and invoice_status. These support account access and payment-intent tracking on the local machine. Invoice creation requires both an authorized amount and a previously saved intent ID.

How it works

Install the pinned Python dependencies in an isolated environment, then start the process with python server.py --stdio. An MCP client connects to that local stdio process. The earlier public HTTP MCP endpoint on the development host has been retired, and the provided material does not advertise a replacement public HTTP endpoint.

The 1NFER Inference Discovery MCP server does not require keys or paid calls for its inspection functions. Account-related operations use locally stored credentials and invoice intents instead. The state directory is private by default, with restrictive permissions for the directory and its files; secrets are not returned as tool outputs.

Setup and configuration

Keep the local state directory between sessions so account access continues to work. By default, state is stored in ~/.config/1nfer-client. Set INFER_STATE_DIR to choose another private directory. The README describes this state as an API credential, not a cryptocurrency wallet seed.

Use an isolated Python environment for the pinned dependencies. Before creating an invoice or relying on payment information, read the live payment terms and verify the rates associated with the relevant account.

Tools and capabilities

• Inspect 1NFER model catalogue entries and exact model aliases.
• Review crypto funding terms.
• Check task cost information without paid inference calls.
• Register a local account.
• Check account status.
• Create an invoice from an authorized amount and saved intent ID.
• Check invoice status.

Limitations and notes

The server does not sign or send cryptocurrency. After an invoice expires, do not initiate a new transfer; wait for confirmed credit. An unknown payment result requires reconciliation rather than a new key or payment.

The documentation makes no guarantee of customers, returns, a free model, or compatibility with a complete framework. A provider name by itself does not prove model provenance. The listed model names are exact catalogue aliases, so callers should use the documented aliases rather than infer alternate names. The supplied README also does not specify client-specific configuration or a public production endpoint.