
Lexicon
io.github.nadine302324-commitsPublished by GitHub account nadine302324-commitsv1.0.0Updated Oct 27, 2026
Comparison intelligence: live evidence from 20 sources, PESTLE/VS/Deep Research frameworks.
Overview
Lexicon is a hosted comparison-intelligence server that gives an assistant vendor head-to-head comparisons, PESTLE research, outage and refund signals, and…
- What you can do
- Compare two vendors or products head-to-head
- Run PESTLE Triangulation deep research on a single vendor
- Pull topic-specific competitive intelligence
- Monitor live outages, reliability, refund rates and customer satisfaction signals
- Retrieve a competitive intelligence feed for a market or industry
- When to use it
- Useful when an assistant needs sourced competitive or vendor research: choosing between two products, profiling a vendor, or tracking reliability and customer-satisfaction signals in a market.
- Requirements
- A remote MCP endpoint (streamable HTTP) at the provider's hosted address; no local runtime is required, though Docker and self-hosted Node.js options are documented. A free API key is available and passed as the LEXICON_API_KEY environment variable or an apiKey setting; the hosted endpoint is also testable without a key under rate limits.
Installation
In SourceWeft
- Open Lexicon in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.nadine302324-commits%2Flexicon/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"lexicon": {
"type": "http",
"url": "https://dbssearch.today/mcp/v1"
}
}
}README
Lexicon Comparison Intelligence MCP Server
Live comparison intelligence for autonomous agents — evidence from 20 independent sources, PESTLE Triangulation, Head-to-Head VS, and Deep Research frameworks.
Live hosted endpoint: https://dbssearch.today/mcp/v1
Tools
Quickstart (Claude Desktop / Cursor)
Or run locally with Docker:
Self-hosted
Auth
Get a free API key at dbssearch.today. Set LEXICON_API_KEY env var, or pass apiKey in Smithery config.
The hosted endpoint at https://dbssearch.today/mcp/v1 is freely testable without a key (rate-limited).
Marketplace
Open agent marketplace with free test endpoint:
POST https://dbssearch.today/marketplace/v1/test
Agent card: https://dbssearch.today/.well-known/agent.json
License
MIT
Source: README.md at commit 1a212cd
Tools
0Version history
1- v1.0.0LatestSep 16, 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 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 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