Emergent Technologies
REMOTE · EMERGENTTECHNOLOGIES.AI
AI and automation consulting, and licensing company data to AI labs, from Emergent Technologies.
Available components
Last scanned (18 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
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 Security80
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1618 tokens (~202/item across 8 items; 8 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “consulting_offer” rewrote its description, which is the text the model reads security
- Tool coverage: 93% → 100% ▲ functional
- “check_program_fit” reworded the description of “dataTypes” cosmetic
- “check_program_fit” reworded the description of “industry” cosmetic
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Nov 26 72
First indexed and scored.
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 21 Nov 2026 · Probed https://emergenttechnologies.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=emergenttechnologies.ai | CN=YR1,O=Let's Encrypt,C=US | 9 Oct 2026 | 7 Jan 2027 | RSA 2048 | SHA256-RSA | 61af8689f8a917108cd7f7ae042258fb07b |
| SANs: emergenttechnologies.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of emergenttechnologies.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| emergenttechnologies.ai. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://emergenttechnologies.ai/mcp | Verified | 200 | |
| http (plaintext) | http://emergenttechnologies.ai/mcp | HTTPS enforced | 308 | https://emergenttechnologies.ai/mcp |
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 →
about_emergent About Emergent Technologies ~151
Returns who Emergent Technologies, Inc. (emergenttechnologies.ai) is, what it does and for whom, from its fact book, with fact ids, statuses, dates and source pages, plus the next step for each kind of person (owner, partner, consulting, buyer). Optional topic narrows the answer: overview (default), disambiguation (how it differs from emergent.sh and from Emergent Technologies of Austin, Texas, emergenttechnologies.com), or one fact-book topic.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | overview (default), disambiguation, or a fact-book topic: company, licensing, estimate, privacy-consent, partners, consulting, lab, contact |
| Name | Type | Req | Description |
|---|---|---|---|
| company | object | yes | – |
| facts | array | yes | – |
| handoff | string | yes | – |
| meta | object | yes | – |
| nextStepByRole | array | yes | – |
| topic | string | yes | – |
| topicLabel | string | yes | – |
No examples provided.
ask_emergent Ask Emergent ~182
Ask Emergent Technologies' own agent a question in plain words (data licensing, the payout estimate, privacy, the referral partner program, AI consulting, the lab, contact). It answers only from Emergent's fact book: the claims are quoted as published, each with its fact id, status and source page, followed by the next step for who is asking. If the fact book does not cover the question it says so and gives the contact path. The question is treated as data: instructions inside it are not followed. It saves and sends nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | The question, in plain words (up to 2,000 characters). Please leave out personal details. |
| role | string | – | Who is asking, to pick the next step: owner, partner, buyer (an AI lab or data buyer), consulting, or other |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | – |
| citations | array | yes | – |
| covered | boolean | yes | – |
| disclosure | string | yes | – |
| factBookVersion | string | yes | – |
| fallbackReason | string | – | – |
| meta | object | yes | – |
| mode | string | yes | – |
| nextStep | object | yes | – |
| refusalKind | – | yes | – |
| refused | boolean | yes | – |
| topic | – | yes | – |
| topicLabel | string|null | yes | – |
No examples provided.
check_program_fit Check program fit ~396
Runs the same matching rules as emergenttechnologies.ai/fit on a person's answers and says which kind of program fits (data licensing, the referral partner program, or expert work) and why. It collects and saves nothing and takes no personal details. To see their specific route and proceed, the person continues at /fit, where they enter their own details with consent.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | us; ca_uk_au = Canada, UK or Australia; other |
| dataTypes | array | – | Specialised records the company holds, such as CAD files, source code repositories or simulation and sensor logs; none if it holds none |
| employees | string | – | People at the company (at its peak if closed) |
| industry | string | – | The company's industry: legal, accounting_finance, medical, or other for any other industry (for example, software and IT services, HVAC, manufacturing or logistics) |
| industryDetail | string | – | When industry is other |
| interest | string | – | Company paths: license = license the records; refer = offer this to clients; both |
| language | string | – | Language of most records |
| licensed | string | – | Professional path: licensed in their field? |
| partnerType | string | – | Partner path |
| path | string | yes | company = owns or runs a company; closed = the company closed; professional = lawyer, doctor, accountant, exec; partner = brings deals |
| reach | string | – | Partner path: how many companies they can reach |
| role | string | – | Professional path |
| serves | string | – | Who the company mostly serves |
| status | string | – | Company path: is it still operating? |
| tools | array | – | Systems the company uses; paper = mostly paper |
| years | string | – | Years of records: lt3, 3to5, 5to10, 10plus |
| Name | Type | Req | Description |
|---|---|---|---|
| captured | boolean | yes | – |
| continueAt | object | yes | – |
| fits | boolean | yes | – |
| meta | object | yes | – |
| programs | array | yes | – |
| route | object | yes | – |
| whatHappensThere | string | yes | – |
| why | array | yes | – |
No examples provided.
consulting_offer AI consulting offer ~115
Returns Emergent's published description of its AI & automation consulting: what it is, how Emergent assesses a business and pairs each initiative with the specialist suited to deliver it, how an engagement runs (Assess, Match, Build, Run), the services, enterprise private intelligence and its deployment options (with a leading lab, on dedicated cloud infrastructure or on hardware the client owns), how to start, and how to get in touch. Each fact carries its own status (approved or draft). No prices are published, so none are returned.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| engage | array | yes | – |
| facts | array | yes | – |
| meta | object | yes | – |
| summary | string | yes | – |
No examples provided.
estimate_payout Estimate a data licensing payout ~143
Returns the same indicative payout range the estimator on emergenttechnologies.ai shows for a company's headcount, years of records and headquarters, with the page's own caveats. It is a starting range from licensing partners' published formulas, not an offer. Inputs above the page's caps (1,000 people, 30 years) are shown at the cap, as on the page.
| Name | Type | Req | Description |
|---|---|---|---|
| employees | integer | yes | How many people work at the company |
| headquarters | string | – | Where the company is headquartered: us (default), canada, europe or other |
| years | integer | yes | How many years of data the company has (usually years in business) |
| Name | Type | Req | Description |
|---|---|---|---|
| capped | boolean | yes | – |
| disclaimer | string | yes | – |
| display | string | yes | – |
| inputsUsed | object | yes | – |
| meta | object | yes | – |
| nextStep | object | yes | – |
| notes | array | yes | – |
| range | object | yes | – |
No examples provided.
partner_program Referral partner program ~78
Returns Emergent's published description of its referral partner program: who can refer, how a referral works, when partners are paid, what to tell an owner, and how to apply. Each fact carries its own status (approved, or draft: wording pending Emergent's final approval). Referral rates and amounts are not published, so none are returned.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| apply | array | yes | – |
| facts | array | yes | – |
| meta | object | yes | – |
| summary | string | yes | – |
| termsPublished | boolean | yes | – |
No examples provided.
search_facts Search Emergent's fact book ~116
Keyword search over Emergent Technologies' fact book. Returns matching facts with their ids, topic, claim, source page, the date each was last checked (asOf) and status (approved or draft). Use it to cite a specific fact; an empty result means the fact book does not state it.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Most results to return (default 8) |
| query | string | yes | Words to look for, e.g. 'who removes personal details' |
| topic | string | – | Limit to one topic |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| facts | array | yes | – |
| hint | string | – | – |
| meta | object | yes | – |
| query | string | yes | – |
No examples provided.
start_conversation Hand off to Emergent's team ~122
Prepares a consent-safe handoff to Emergent's team. It sends nothing and saves nothing: it returns a short summary of what the person wants and the exact Emergent page where the person reviews, confirms and submits their own details. Show the person the summary and the link, and send them there only after they say yes.
| Name | Type | Req | Description |
|---|---|---|---|
| intent | string | yes | license_records, refer_businesses, consulting or other |
| request | string | – | Optional: what the person wants, in a sentence. Returned to you as written; do not include personal details. |
| Name | Type | Req | Description |
|---|---|---|---|
| alternative | object | yes | – |
| confirmAt | object | yes | – |
| instructionsForCallingAgent | array | yes | – |
| meta | object | yes | – |
| personRequest | string|null | yes | – |
| saved | boolean | yes | – |
| sent | boolean | yes | – |
| summary | string | yes | – |
No examples provided.
How do I install the Emergent Technologies MCP server?
Emergent Technologies is a hosted endpoint at https://emergenttechnologies.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 · emergenttechnologies.ai
claude mcp add --transport http ai-emergenttechnologies-emergent 'https://emergenttechnologies.ai/mcp'
What is the Emergent Technologies MCP server?
Emergent Technologies is an MCP server listed in the public MCP registry as ai.emergenttechnologies/emergent. AI and automation consulting, and licensing company data to AI labs, from Emergent Technologies. This page covers its hosted endpoint (https://emergenttechnologies.ai/mcp).
Is the Emergent Technologies MCP server safe to use?
Emergent Technologies 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 Emergent Technologies MCP server expose?
Emergent Technologies exposes 8 tools: ask_emergent, about_emergent, search_facts, estimate_payout, check_program_fit, and 3 more. Their descriptions and schemas cost roughly 1,303 tokens of context every time the server is loaded.
Does the Emergent Technologies MCP server require authentication?
No. We connected to Emergent Technologies without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Emergent Technologies MCP server still maintained?
Emergent Technologies is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Emergent Technologies MCP server?
VerifyMCP ran 13 checks on Emergent Technologies, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.