# 爱给 AI MCP (remote · www.aigei.com)

搜索音效、配乐、视频和图片作品，查看详情、预览并获取文件，通过浏览器 OAuth 授权连接爱给账号。

- Trust score: 31/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `www.aigei.com`: 31/100 (this document), [markdown](https://verifymcp.io/servers/com-aigei-mcp/www.md), [page](https://verifymcp.io/servers/com-aigei-mcp/www)

## Channel facts

- Endpoint: `https://www.aigei.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.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**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the 爱给 AI MCP server?

爱给 AI MCP is a hosted endpoint at https://www.aigei.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-aigei-mcp 'https://www.aigei.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-aigei-mcp": {
      "url": "https://www.aigei.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-aigei-mcp]
url = "https://www.aigei.com/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-aigei-mcp:
    url: "https://www.aigei.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-aigei-mcp": {
      "type": "http",
      "url": "https://www.aigei.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-16 (score 31)

First indexed and scored.

## MCP tools (0)

No tool schema has been captured from this endpoint yet.

## Diagnostics

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

## Score history

- 2026-11-21: 31
- 2026-11-20: 31
- 2026-11-19: 31
- 2026-11-18: 31
- 2026-11-17: 31
- 2026-11-16: 31

## Common questions

### What is the 爱给 AI MCP server?

爱给 AI MCP is listed in the public MCP registry as com.aigei/mcp. 搜索音效、配乐、视频和图片作品，查看详情、预览并获取文件，通过浏览器 OAuth 授权连接爱给账号。 This page covers its hosted endpoint (https://www.aigei.com/mcp).

### Is the 爱给 AI MCP server safe to use?

爱给 AI MCP scores 31 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.

### Does the 爱给 AI MCP server require authentication?

Yes. 爱给 AI MCP asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the 爱给 AI MCP server still maintained?

爱给 AI MCP 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 爱给 AI MCP server?

VerifyMCP ran 4 checks on 爱给 AI MCP, covering TLS certificate, Authorization, HSTS header and DNSSEC. 7 items could not be completed, a gap on our side rather than a finding about 爱给 AI MCP: HTTPS, Transport, Schema quality, Stability and 3 more. 6 categories score 0 for that reason, because we only credit what we can confirm. 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://www.aigei.com/mcp
- Website: https://www.aigei.com/open/mcpPage
- Changelog RSS feed: https://verifymcp.io/servers/com-aigei-mcp/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-aigei-mcp/www/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-aigei-mcp/www.json
- HTML version of this page: https://verifymcp.io/servers/com-aigei-mcp/www
