# EmpireGit (remote · empiregit.eliteaiempire.com)

EmpireGit

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

## Components

- remote · `empiregit.eliteaiempire.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-eliteaiempire-empiregit/empiregit.md), [page](https://verifymcp.io/servers/com-eliteaiempire-empiregit/empiregit)

## Channel facts

- Endpoint: `https://empiregit.eliteaiempire.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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**: 74/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.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 61/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 545 tokens (~68/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 71% of tool parameters carry a description.
- **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 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the EmpireGit MCP server?

EmpireGit is a hosted endpoint at https://empiregit.eliteaiempire.com/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 com-eliteaiempire-empiregit 'https://empiregit.eliteaiempire.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-eliteaiempire-empiregit": {
      "url": "https://empiregit.eliteaiempire.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-eliteaiempire-empiregit": {
      "type": "http",
      "url": "https://empiregit.eliteaiempire.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-eliteaiempire-empiregit]
url = "https://empiregit.eliteaiempire.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-eliteaiempire-empiregit --url 'https://empiregit.eliteaiempire.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-eliteaiempire-empiregit:
    url: "https://empiregit.eliteaiempire.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-eliteaiempire-empiregit": {
      "Transport": "http",
      "Url": "https://empiregit.eliteaiempire.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-eliteaiempire-empiregit -t streamable-http -u 'https://empiregit.eliteaiempire.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-eliteaiempire-empiregit": {
      "type": "http",
      "url": "https://empiregit.eliteaiempire.com/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-20 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 70, +1)

- [functional regression] Schema quality: 53 → 68
- [functional improvement] Tool coverage: 50% → 71%
- [cosmetic] “get_checkout_link” added an optional parameter “accept_terms”
- [cosmetic] “get_checkout_link” added an optional parameter “buyer_email”
- [cosmetic] “get_checkout_link” added an optional parameter “store_handle”

### 2026-11-17 (score 69, +1)

- [security] Tool “get_checkout_link” rewrote its description, which is the text the model reads

### 2026-11-15 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 67, −2)

- [security regression] HSTS header: pass → fail
- [functional improvement] Schema quality: 59 → 49
- [functional] First check of Tool coverage: 50
- [functional] New tool “get_checkout_link”
- [functional] New tool “get_company_info”
- [functional] New tool “list_pricing”
- [functional] New tool “search_site”

### 2026-11-12 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 68, +1)

- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security improvement] Transport: fail → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.07

### 2026-11-10 (score 67, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

## MCP tools (8)

### `git_overview` (~78 tokens)

Returns what Empire Git does and the Empire Cloud tools that work with it. Pricing: {"unit": "call", "price_usd": 0, "free_quota": "200 per day per IP", "note": "Keyed volume pricing is published at https://empiregit.eliteaiempire.com/pricing"}.

### `git_about` (~70 tokens)

What Empire Git does and what is free Pricing: {"unit": "call", "price_usd": 0, "free_quota": "200 per day per IP", "note": "Keyed volume pricing is published at https://empiregit.eliteaiempire.com/pricing"}.

### `git_pricing` (~70 tokens)

Where prices live and what costs nothing Pricing: {"unit": "call", "price_usd": 0, "free_quota": "200 per day per IP", "note": "Keyed volume pricing is published at https://empiregit.eliteaiempire.com/pricing"}.

### `usage_get` (~19 tokens)

Usage for the calling key (last 30 days)

### `get_company_info` (~30 tokens)

Company info

What this company sells, who it is for, and every agent/API entry point. No account needed.

### `list_pricing` (~34 tokens)

Pricing

Current plans and prices in USD: plan, interval, amount_usd, currency, what_you_get. No account needed.

### `get_checkout_link` (~206 tokens)

Checkout link

Checkout URL for a plan. With no arguments: the main paid plan. Where the site supports it the URL is a Stripe-hosted Checkout session (created unpaid; a human pays, nothing is charged by this tool). A free plan is only returned when the plan is requested or the company sells nothing else.

Input parameters:

- `accept_terms` (boolean): ONLY where the site requires the buyer to accept its Terms/refund policy before checkout: set true only after the human buyer has read and accepted the policy links the tool lists. Never set it on yo…
- `buyer_email` (string): only for sites that need the buyer's email or store handle before checkout: the human buyer's own receipt email
- `interval` (string)
- `plan` (string): plan name from list_pricing
- `store_handle` (string): only where the site asks for it (StoreForge): the store handle the buyer chose, 3+ chars a-z 0-9 -

### `search_site` (~38 tokens)

Search this site

Find pages on this site by keyword; returns url, title and summary.

Input parameters:

- `limit` (integer)
- `query` (string, required): keywords

## Diagnostics

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

## Score history

- 2026-11-21: 71
- 2026-11-20: 71
- 2026-11-19: 70
- 2026-11-18: 70
- 2026-11-17: 69
- 2026-11-16: 68
- 2026-11-15: 68
- 2026-11-14: 67
- 2026-11-13: 67
- 2026-11-12: 69
- 2026-11-11: 68
- 2026-11-10: 67
- 2026-11-09: 67

## Common questions

### What is the EmpireGit MCP server?

EmpireGit is an MCP server listed in the public MCP registry as com.eliteaiempire/empiregit. EmpireGit. This page covers its hosted endpoint (https://empiregit.eliteaiempire.com/mcp).

### Is the EmpireGit MCP server safe to use?

EmpireGit scores 71 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 EmpireGit MCP server expose?

EmpireGit exposes 8 tools: git_overview, git_about, git_pricing, usage_get, get_company_info, and 3 more. Their descriptions and schemas cost roughly 545 tokens of context every time the server is loaded.

### Does the EmpireGit MCP server require authentication?

No. We connected to EmpireGit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the EmpireGit MCP server still maintained?

EmpireGit 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 EmpireGit MCP server?

VerifyMCP ran 13 checks on EmpireGit, 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://empiregit.eliteaiempire.com/mcp
- Website: https://empiregit.eliteaiempire.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-eliteaiempire-empiregit/empiregit.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-eliteaiempire-empiregit/empiregit/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-eliteaiempire-empiregit/empiregit.json
- HTML version of this page: https://verifymcp.io/servers/com-eliteaiempire-empiregit/empiregit
