
ModelLens
io.github.GreatbeingPublished by GitHub account Greatbeingv0.1.3Updated Nov 7, 2026
See which models actually work: probe, rank and recommend across OpenAI-compatible gateways.
The publisher's own server: model.tools — Zero-Auth Agent Utilities
Overview
Probes OpenAI-compatible model gateways, ranks models by measured latency and success, and recommends which model to use.
- What you can do
- List the models each configured endpoint advertises, with an optional substring filter
- Probe models with real requests, measuring latency, success, streaming and tool calling
- Rank models from recorded probe history and recommend the best one for a fast, cheap or capable profile
- Produce a markdown report of the whole picture across endpoints
- Also runs as a command-line tool for one-off probe or ranking runs
- When to use it
- Useful when you run several model providers or an aggregating gateway and want evidence of which models actually answer, how fast, and which one a router should pick. Also handy when onboarding a new provider or when a provider starts failing silently.
- Requirements
- Runs locally as a Python 3.9+ process with no third-party dependencies (PyPI package modellens-mcp or a single script). Needs a JSON endpoint configuration file passed via MODELLENS_CONFIG, containing each endpoint's base URL and optional API key, and a history file path via MODELLENS_DATA. Network access to the configured gateways is required.
Installation
In SourceWeft
- Open ModelLens in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
ModelLens
See which of your models actually works.
An MCP server that turns any OpenAI-compatible gateway into an observable, rankable set of models. It discovers what a provider advertises, probes what works right now — latency, success, cancellation, streaming, tool calling — keeps the history, and answers "which model should I use?"
Zero third-party dependencies. Python 3.9+ standard library only.
[PyPI version] [PyPI downloads] [MCP Registry] [Glama] [Live status]
Why
If you run more than one model provider, you already have this problem:
- The gateway says it serves 89 models. How many actually answer?
- Which one is fast today? Yesterday's answer is already stale.
- Your router picks the first entry in a list — and the first entry is slow.
- Failures are invisible until a user complains.
ModelLens makes that visible. It is the difference between trusting a model list and measuring it.
Real example from a live gateway (89 models, 16 probed):
The default routing group was putting an 87-second model first and a 0.9-second model third. ModelLens found that in one pass.
Install
or straight from source — no dependencies, no install step:
Configure
api_key may be empty for a localhost gateway. models optionally filters the
advertised list; enabled: false disables an endpoint without deleting it.
Run as an MCP server
Point any MCP client at it:
Works with Claude Desktop, Cursor, Windsurf, VS Code, and any other MCP client.
DeepSeek Harness
Register it in the profile's cordis.patch.yml (note: a new entry needs
- insert:, not a bare - id: — a bare one means "modify an existing entry"):
Then restart dsh web. Verified: the server runs as a child process of
dsh-web (pgrep -P $(systemctl --user show dsh-web -p MainPID)).
Tools
Example
Hosted / paid (x402, USDC on Base)
A hosted endpoint runs the same tools over MCP streamable-HTTP and charges per call with x402 — agents pay gasless USDC on Base, no accounts or API keys:
- Endpoint:
https://8000-agqz7vbdiiy6cc2n2tbs63iji4.instabox.tech/mcp - Manifest:
/.well-known/x402(payTo address, prices, facilitator) - Prices:
list_modelsfree ·ranking/recommend$0.01 ·report$0.02 ·probe$0.05 (probe makes real upstream requests, so it costs the most)
An unpaid paid-tool call returns HTTP 402 + PAYMENT-REQUIRED; the agent
signs an EIP-3009 USDC transfer and retries with X-PAYMENT, the facilitator
verifies/settles, and the tool result comes back with a PAYMENT-RESPONSE.
Self-host the same server anywhere with python3 server_x402.py
(set X402_PAY_TO to your receiving address; see server_x402.py header).
How it scores
Every probe is a real request, so the numbers are evidence, not estimates.
Verdicts: healthy (≥95% success, <3 s median) · mixed · unreliable
(≥30% cancelled) · quota_blocked (all 429) · dead (all 404) · untested.
History is kept per model (newest 200 probes) in history.json, so rankings
improve as you use it.
CLI
The server doubles as a command-line tool:
Use cases
- Before you pick a model —
recommend(profile="fast") - When a provider goes quiet —
rankingshows it dropping before your users do - When your router misbehaves — compare group members, find the slow one
- Cost control — spot the expensive model that is never chosen
- Onboarding a new provider — probe once, see what actually works
Status and roadmap
Working today: discovery, probing, streaming/tool-call checks, scoring, ranking, recommendation, markdown report, MCP stdio transport, CLI.
Roadmap: OpenAI-compatible /v1/models only for now; Anthropic and Gemini
transports, per-endpoint cost accounting, alerting webhooks, and a hosted
multi-team version.
License
MIT. Use it, ship it, charge for your own hosted version.
Honest notes
- Probing costs tokens. Each probe is a real completion. Keep
limitsensible and don't probe a hundred models every minute. - A single probe is weak evidence. The score is meaningful after several
probes; the report says
n=1so you can see the sample size. - Latency depends on you. Your network, not just the provider, is in the measurement. Run it from where your agents run.
Source: README.md at commit 5bdfd65
Tools
0Version history
2- v0.1.3LatestNov 7, 2026
- v0.1.2Nov 5, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Model integrations

model.tools — Zero-Auth Agent Utilities
tools.modelOfficial publisher
Zero-auth remote utility server giving agents disposable email OTP reading, durable checkpoints, webhook bins, wake timers, receipts and page-to-Markdown…
NLP.COM.AI Open Model Catalog
ai.com.nlpOfficial publisher
NLP.COM.AI Open Model Catalog's hosted MCP server, published by nlp.com.ai; no sign-in required; Streamable HTTP; 3 tools.

Hologram Model Hub
foundation.uor.hubOfficial publisher
A remote MCP server that lets an assistant search an index of open models and get verified download links with SHA-256 checksums.

Bedrock Multi-Model
Published by GitHub account Sagargupta16
Local MCP server that puts AWS Bedrock's text, image, video and embedding models behind nine tools so an assistant can ask, compare and judge models.

Veqen Pricing: AI model costs
Published by GitHub account Keyveve
Read-only MCP server exposing Veqen's public AI model price book to look up rates, compare models and estimate workload costs in USD.