# Emergent Technologies (remote · emergenttechnologies.ai)

AI and automation consulting, and licensing company data to AI labs, from Emergent Technologies.

- Trust score: 76/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `emergenttechnologies.ai`: 76/100 (this document), [markdown](https://verifymcp.io/servers/ai-emergenttechnologies-emergent/emergenttechnologies.md), [page](https://verifymcp.io/servers/ai-emergenttechnologies-emergent/emergenttechnologies)

## Channel facts

- Endpoint: `https://emergenttechnologies.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http ai-emergenttechnologies-emergent 'https://emergenttechnologies.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-emergenttechnologies-emergent": {
      "url": "https://emergenttechnologies.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-emergenttechnologies-emergent": {
      "type": "http",
      "url": "https://emergenttechnologies.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-emergenttechnologies-emergent]
url = "https://emergenttechnologies.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-emergenttechnologies-emergent": {
      "type": "remote",
      "url": "https://emergenttechnologies.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-emergenttechnologies-emergent --url 'https://emergenttechnologies.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-emergenttechnologies-emergent:
    url: "https://emergenttechnologies.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-emergenttechnologies-emergent": {
      "Transport": "http",
      "Url": "https://emergenttechnologies.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-emergenttechnologies-emergent -t streamable-http -u 'https://emergenttechnologies.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-emergenttechnologies-emergent": {
      "type": "http",
      "url": "https://emergenttechnologies.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 76, +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.

### 2026-11-19 (score 75, +1)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-11-17 (score 74, +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.

### 2026-11-16 (score 73, 0)

- [security] 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
- [functional improvement] Tool coverage: 93% → 100%
- [cosmetic] “check_program_fit” reworded the description of “dataTypes”
- [cosmetic] “check_program_fit” reworded the description of “industry”

### 2026-11-15 (score 73, +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.

### 2026-11-14 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-13 (score 72)

First indexed and scored.

## MCP tools (8)

### `ask_emergent` (~182 tokens)

Ask Emergent

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.

Input parameters:

- `question` (string, required): 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

Output parameters:

- `answer` (string)
- `citations` (array)
- `covered` (boolean)
- `disclosure` (string)
- `factBookVersion` (string)
- `fallbackReason` (string)
- `meta` (object)
- `mode` (string)
- `nextStep` (object)
- `refusalKind`
- `refused` (boolean)
- `topic`
- `topicLabel` (string|null)

### `about_emergent` (~151 tokens)

About Emergent Technologies

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.

Input parameters:

- `topic` (string): overview (default), disambiguation, or a fact-book topic: company, licensing, estimate, privacy-consent, partners, consulting, lab, contact

Output parameters:

- `company` (object)
- `facts` (array)
- `handoff` (string)
- `meta` (object)
- `nextStepByRole` (array)
- `topic` (string)
- `topicLabel` (string)

### `search_facts` (~116 tokens)

Search Emergent's fact book

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.

Input parameters:

- `limit` (integer): Most results to return (default 8)
- `query` (string, required): Words to look for, e.g. 'who removes personal details'
- `topic` (string): Limit to one topic

Output parameters:

- `count` (number)
- `facts` (array)
- `hint` (string)
- `meta` (object)
- `query` (string)

### `estimate_payout` (~143 tokens)

Estimate a data licensing payout

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.

Input parameters:

- `employees` (integer, required): How many people work at the company
- `headquarters` (string): Where the company is headquartered: us (default), canada, europe or other
- `years` (integer, required): How many years of data the company has (usually years in business)

Output parameters:

- `capped` (boolean)
- `disclaimer` (string)
- `display` (string)
- `inputsUsed` (object)
- `meta` (object)
- `nextStep` (object)
- `notes` (array)
- `range` (object)

### `check_program_fit` (~396 tokens)

Check program fit

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.

Input parameters:

- `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, required): 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

Output parameters:

- `captured` (boolean)
- `continueAt` (object)
- `fits` (boolean)
- `meta` (object)
- `programs` (array)
- `route` (object)
- `whatHappensThere` (string)
- `why` (array)

### `partner_program` (~78 tokens)

Referral partner program

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.

Output parameters:

- `apply` (array)
- `facts` (array)
- `meta` (object)
- `summary` (string)
- `termsPublished` (boolean)

### `consulting_offer` (~115 tokens)

AI consulting offer

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.

Output parameters:

- `engage` (array)
- `facts` (array)
- `meta` (object)
- `summary` (string)

### `start_conversation` (~122 tokens)

Hand off to Emergent's team

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.

Input parameters:

- `intent` (string, required): 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.

Output parameters:

- `alternative` (object)
- `confirmAt` (object)
- `instructionsForCallingAgent` (array)
- `meta` (object)
- `personRequest` (string|null)
- `saved` (boolean)
- `sent` (boolean)
- `summary` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-emergenttechnologies-emergent/emergenttechnologies#diagnostics

## Score history

- 2026-11-21: 76
- 2026-11-20: 75
- 2026-11-19: 75
- 2026-11-18: 74
- 2026-11-17: 74
- 2026-11-16: 73
- 2026-11-15: 73
- 2026-11-14: 72
- 2026-11-13: 72

## Common questions

### 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.

## Links

- Remote endpoint: https://emergenttechnologies.ai/mcp
- Repository: https://github.com/Free-LLC/emergent-mcp
- Website: https://emergenttechnologies.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-emergenttechnologies-emergent/emergenttechnologies.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-emergenttechnologies-emergent/emergenttechnologies/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-emergenttechnologies-emergent/emergenttechnologies.json
- HTML version of this page: https://verifymcp.io/servers/ai-emergenttechnologies-emergent/emergenttechnologies
