ai.echoloc/company-technographics
REMOTE · API.ECHOLOC.AI · SCANNED OCT 4
Search 760K+ companies by technographics with direction of change: adopting, replacing, evaluating
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 413 tokens (~137/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 25% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the ai.echoloc/company-technographics MCP server?
ai.echoloc/company-technographics is a hosted endpoint at https://api.echoloc.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.echoloc.ai
claude mcp add --transport http ai-echoloc-company-technographics 'https://api.echoloc.ai/mcp'
{
"mcpServers": {
"ai-echoloc-company-technographics": {
"url": "https://api.echoloc.ai/mcp"
}
}
} {
"servers": {
"ai-echoloc-company-technographics": {
"type": "http",
"url": "https://api.echoloc.ai/mcp"
}
}
} [mcp_servers.ai-echoloc-company-technographics] url = "https://api.echoloc.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-echoloc-company-technographics": {
"type": "remote",
"url": "https://api.echoloc.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-echoloc-company-technographics --url 'https://api.echoloc.ai/mcp' --transport streamable-http
mcp_servers:
ai-echoloc-company-technographics:
url: "https://api.echoloc.ai/mcp" {
"McpServers": {
"ai-echoloc-company-technographics": {
"Transport": "http",
"Url": "https://api.echoloc.ai/mcp"
}
}
} assistant mcp add ai-echoloc-company-technographics -t streamable-http -u 'https://api.echoloc.ai/mcp'
{
"mcpServers": {
"ai-echoloc-company-technographics": {
"type": "http",
"url": "https://api.echoloc.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 30 Sept 26 −1
- Tool “get_company_by_domain” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “get_company_by_domain” reworded the description of “domain” cosmetic
- 28 Sept 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Aug 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 19 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Oct 2026 · Probed https://api.echoloc.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=echoloc.ai | CN=WE1,O=Google Trust Services,C=US | 20 Sept 2026 | 19 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d8b396bf2868f9a51396a31456116338 |
| SANs: echoloc.ai, *.echoloc.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.echoloc.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| echoloc.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.echoloc.ai/mcp | Verified | 200 | |
| http (plaintext) | http://api.echoloc.ai/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_company_by_domain Get company profile by domain ~86
Resolve a company domain (e.g. 'walgreens.com') to its full profile: firmographics, hiring stats, and the technology stack with adoption context (using / adopting / replacing / evaluating). Matches the primary domain first, then known aliases (regional TLDs, legacy brands, subdomains).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Company domain — primary or any known alias |
No output schema declared.
No examples provided.
list_technologies List tracked technologies ~59
Catalog of all technologies in the dataset with per-technology company counts. sort='count' (most used first) or 'name'.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | – |
| page_size | integer | – | – |
| sort | string | – | – |
No output schema declared.
No examples provided.
search_companies_by_technologies Search companies by technologies ~114
Find companies using the given technologies, ranked by usage. Names are case-insensitive ('snowflake' == 'Snowflake'); 10,000+ technologies are tracked (use list_technologies to explore). match='any' needs at least one technology, 'all' needs every one.
| Name | Type | Req | Description |
|---|---|---|---|
| match | string | – | – |
| page | integer | – | – |
| page_size | integer | – | – |
| technologies | array | yes | Technology names, e.g. ["Snowflake", "dbt"] |
No output schema declared.
No examples provided.
What is the ai.echoloc/company-technographics MCP server?
ai.echoloc/company-technographics is an MCP server listed in the public MCP registry as ai.echoloc/company-technographics. Search 760K+ companies by technographics with direction of change: adopting, replacing, evaluating. This page covers its hosted endpoint (https://api.echoloc.ai/mcp).
Is the ai.echoloc/company-technographics MCP server safe to use?
ai.echoloc/company-technographics scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ai.echoloc/company-technographics MCP server expose?
ai.echoloc/company-technographics exposes 3 tools: search_companies_by_technologies, get_company_by_domain, list_technologies. Their descriptions and schemas cost roughly 259 tokens of context every time the server is loaded.
Does the ai.echoloc/company-technographics MCP server require authentication?
No. We connected to ai.echoloc/company-technographics without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ai.echoloc/company-technographics MCP server still maintained?
ai.echoloc/company-technographics is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.