# Contribution Exchange (remote · signalaf.com)

Contribution Exchange MCP: domain discovery, policies, preflight, proposals, and signals.

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `signalaf.com`: 84/100 (this document), [markdown](https://verifymcp.io/servers/com-signalaf-contribution-exchange/api-exchange-mcp.md), [page](https://verifymcp.io/servers/com-signalaf-contribution-exchange/api-exchange-mcp)

## Channel facts

- Endpoint: `https://signalaf.com/api/exchange/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-09-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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 966 tokens (~161/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Contribution Exchange MCP server?

Contribution Exchange is a hosted endpoint at https://signalaf.com/api/exchange/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-signalaf-contribution-exchange 'https://signalaf.com/api/exchange/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-signalaf-contribution-exchange": {
      "url": "https://signalaf.com/api/exchange/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-signalaf-contribution-exchange": {
      "type": "http",
      "url": "https://signalaf.com/api/exchange/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-signalaf-contribution-exchange]
url = "https://signalaf.com/api/exchange/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-signalaf-contribution-exchange": {
      "type": "remote",
      "url": "https://signalaf.com/api/exchange/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-signalaf-contribution-exchange --url 'https://signalaf.com/api/exchange/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-signalaf-contribution-exchange:
    url: "https://signalaf.com/api/exchange/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-signalaf-contribution-exchange": {
      "Transport": "http",
      "Url": "https://signalaf.com/api/exchange/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-signalaf-contribution-exchange -t streamable-http -u 'https://signalaf.com/api/exchange/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-signalaf-contribution-exchange": {
      "type": "http",
      "url": "https://signalaf.com/api/exchange/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-09-20 (score 84, +1)

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

### 2026-09-18 (score 83, +1)

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

### 2026-09-16 (score 82, +1)

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

### 2026-09-14 (score 81, +1)

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

### 2026-09-12 (score 80, +1)

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

### 2026-09-10 (score 79, +1)

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

### 2026-09-07 (score 78, +1)

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

### 2026-09-05 (score 77, +1)

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

## MCP tools (6)

### `exchange_discover_domain` (~124 tokens)

Exchange Discover Domain — Contribution Exchange Profile Lookup

Determine whether a domain publishes a Contribution Exchange profile. Returns the canonical Exchange manifest, policy URLs, signal URLs, and whether the domain is self-hosted or delegated to a Steward. Read-only — does not propose, commit, or authorize anything. Enforces HTTPS, redirect limits, timeouts, and SSRF protections (blocks loopback, link-local, private-network, and metadata-service targets).

Input parameters:

- `domain` (string, required): Domain name or HTTPS URL to check (e.g. 'signalaf.com' or 'https://signalaf.com'). Normalized to hostname.

### `exchange_get_policy` (~75 tokens)

Exchange Get Policy — Domain Exchange Policy

Fetch the canonical Contribution Exchange policy for a domain or its delegated Steward. Returns authority ceilings, consideration limits, human-review requirements, and supported behavior. Read-only — does not mutate state or perform preflight evaluation. Distinguishes a missing policy from an unavailable service.

Input parameters:

- `domain` (string, required): Domain name to fetch policy for.

### `exchange_preflight` (~232 tokens)

Exchange Preflight — Advisory Proposal Policy Evaluation

Evaluate a proposed contribution against the same policy logic used by the real proposal flow. Returns whether the proposal is likely to be auto-engaged, accepted for review, escalated to a human, or rejected as invalid. READ-ONLY: performs no proposal insertion, notification, event creation, or state transition. The result is advisory and time-bound — a favorable preflight does NOT guarantee engagement, Commitment, authorization, payment, or execution. Uses the same evaluateProposal function as the canonical proposal route.

Input parameters:

- `category` (string, required): Contribution category (e.g. 'technical', 'accessibility', 'documentation', 'research').
- `confidence` (object): Confidence in the observation (score 0-1 and basis).
- `consideration` (array): Requested consideration (cash, royalty, reciprocal_access, attribution, referral, other). Advertised consideration is NOT binding until accepted through Commitment.
- `domain` (string, required): Target domain for the proposed contribution.
- `required_authorization` (object): Authority requested (inspect_public, sandbox_test, repository_write, private_data, credential_access, production_modify, deploy, penetration_testing).

### `exchange_list_signals` (~234 tokens)

Exchange List Signals — Domain-Published Work Signals

List domain-published Exchange Signals (problems, requests, challenges, bounties, verification tasks, discoveries, experiments). Read-only. Returns canonical URLs, signal revision, revision hash, and status. Signal status is DISTINCT from exchange status — a signal does not create a Commitment or authorize execution. Supports the same filters and pagination as the HTTP API.

Input parameters:

- `accepting_attempts` (boolean): Only return signals currently accepting attempts.
- `consideration_mode` (string): Filter by consideration mode.
- `cursor` (string): Pagination cursor from a previous response.
- `domain` (string): Filter by publisher domain.
- `expires_before` (string): ISO 8601 timestamp — only signals expiring before this.
- `label` (string): Filter by label.
- `limit` (integer): Maximum signals to return (1-100, default 50).
- `published_after` (string): ISO 8601 timestamp — only signals published after this.
- `status` (string): Filter by signal status.
- `type` (string): Filter by signal type.
- `verification_mode` (string): Filter by verification mode.

### `exchange_get_signal` (~69 tokens)

Exchange Get Signal — Signal Detail by ID

Get full detail for a single Exchange Signal by ID. Read-only. Returns the complete signal including constraints, participation rules, verification configuration, consideration declaration, and follow-on behavior. A signal does NOT create a Commitment, authorize execution, or guarantee payment.

Input parameters:

- `signal_id` (string, required): Signal ID.

### `exchange_get_attempt` (~82 tokens)

Exchange Get Attempt — Signal Attempt Detail

Get detail for a signal attempt. Read-only. Enforces attempt visibility — actors may only read their own private attempts. Returns attempt status and verification result if available. Attempt status is NOT an exchange state. Verification is Steward-controlled and cannot be self-asserted.

Input parameters:

- `attempt_id` (string, required): Attempt ID.
- `signal_id` (string, required): Signal ID.

## Diagnostics

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

## Score history

- 2026-09-21: 84
- 2026-09-20: 84
- 2026-09-19: 83
- 2026-09-18: 83
- 2026-09-17: 82
- 2026-09-16: 82
- 2026-09-15: 81
- 2026-09-14: 81
- 2026-09-13: 80
- 2026-09-12: 80
- 2026-09-11: 79
- 2026-09-10: 79
- 2026-09-09: 78
- 2026-09-08: 78
- 2026-09-07: 78
- 2026-09-06: 77
- 2026-09-05: 77
- 2026-09-04: 76
- 2026-09-03: 76
- 2026-09-02: 75
- 2026-09-01: 75
- 2026-08-31: 74
- 2026-08-30: 74
- 2026-08-29: 73
- 2026-08-28: 73
- 2026-08-27: 72
- 2026-08-26: 72

## Common questions

### What is the Contribution Exchange MCP server?

Contribution Exchange is an MCP server listed in the public MCP registry as com.signalaf/contribution-exchange. Contribution Exchange MCP: domain discovery, policies, preflight, proposals, and signals. This page covers its hosted endpoint (https://signalaf.com/api/exchange/mcp).

### Is the Contribution Exchange MCP server safe to use?

Contribution Exchange scores 84 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 Contribution Exchange MCP server expose?

Contribution Exchange exposes 6 tools: exchange_discover_domain, exchange_get_policy, exchange_preflight, exchange_list_signals, exchange_get_signal, exchange_get_attempt. Their descriptions and schemas cost roughly 816 tokens of context every time the server is loaded.

### Does the Contribution Exchange MCP server require authentication?

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

### Is the Contribution Exchange MCP server still maintained?

Contribution Exchange is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://signalaf.com/api/exchange/mcp
- Repository: https://github.com/SunrisesIllNeverSee/sigrank-app
- Website: https://signalaf.com/exchange
- Changelog RSS feed: https://verifymcp.io/servers/com-signalaf-contribution-exchange/api-exchange-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-signalaf-contribution-exchange/api-exchange-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-signalaf-contribution-exchange/api-exchange-mcp