# com.bagsthatpay/site (remote · bagsthatpay.com)

Bags That Pay: the site's own MCP server — dataset, enquiry, entities, listing (enquiry = a...

- Trust score: 67/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `bagsthatpay.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/com-bagsthatpay-site/bagsthatpay.md), [page](https://verifymcp.io/servers/com-bagsthatpay-site/bagsthatpay)

## Channel facts

- Endpoint: `https://bagsthatpay.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-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 32 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 88/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 2762 tokens (~81/item across 34 items; 32 tools + 2 resources), lean.
  - 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**: 75/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 25% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "listing_pay_card" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 34 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the com.bagsthatpay/site MCP server?

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

### Cursor

```json
{
  "mcpServers": {
    "com-bagsthatpay-site": {
      "url": "https://bagsthatpay.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-bagsthatpay-site]
url = "https://bagsthatpay.com/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-bagsthatpay-site:
    url: "https://bagsthatpay.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-bagsthatpay-site": {
      "type": "http",
      "url": "https://bagsthatpay.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-09-20 (score 67, +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-09-17 (score 66, +1)

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

### 2026-09-15 (score 65, +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-09-13 (score 64, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-12 (score 63)

First indexed and scored.

## MCP tools (32)

### `dataset_columns` (~39 tokens)

Dataset columns and shape

The columns, which of them are numeric, the row count and the provenance banner of the Bags That Pay dataset. Call this first to learn the schema.

### `dataset_search` (~51 tokens)

Search the dataset

Rows of the Bags That Pay dataset whose cells contain the query (case-insensitive), up to 50.

Input parameters:

- `limit` (integer)
- `query` (string, required): text to look for in any cell

### `dataset_row` (~42 tokens)

Look a row up by an exact key

The rows of the Bags That Pay dataset where a column equals a value exactly (case-insensitive).

Input parameters:

- `column` (string, required)
- `value` (string, required)

### `dataset_compare` (~52 tokens)

Compare rows side by side

The rows of the Bags That Pay dataset whose column is any of the given values, in the order given — for "X vs Y" questions.

Input parameters:

- `column` (string, required)
- `values` (array, required)

### `dataset_stats` (~54 tokens)

Summary statistics for a numeric column

count, min, max, mean, median and sum of a numeric column of the Bags That Pay dataset (grouping commas and currency are handled; non-numeric rows are excluded and counted).

Input parameters:

- `column` (string, required)

### `dataset_top` (~65 tokens)

Rank rows by a numeric column

The highest (or lowest) rows of the Bags That Pay dataset by a numeric column — "which is the most/least X".

Input parameters:

- `ascending` (boolean): true for the lowest first; default highest first
- `column` (string, required)
- `limit` (integer)

### `dataset_provenance` (~39 tokens)

Where this data comes from, and how to cite it

The source, the date it was computed, the licence and the citation for the Bags That Pay dataset. Read this to attribute a figure correctly.

### `entities_schema` (~42 tokens)

The register's shape, counts and provenance

Which fields the Bags That Pay register register carries and on how many entities, the regions and services, the identifier schemes, and how to cite it. Call this first.

### `entity_lookup` (~89 tokens)

One entity by its register identifier or slug

The Bags That Pay register entry for a firm, by its register identifier (scheme + value, e.g. lei) or by the slug of its page. Exact match; returns the whole record with its page.

Input parameters:

- `scheme` (string): identifier scheme, e.g. lei, fca_frn, tdlr_license
- `slug` (string)
- `value` (string)

### `entities_search` (~80 tokens)

Search the register

Entities of Bags That Pay register whose name, commercial name, website, address or authority contains the query, optionally within a region (id or name) and a service (slug or name). Up to 50 rows.

Input parameters:

- `limit` (integer)
- `q` (string)
- `region` (string)
- `service` (string)

### `entities_in` (~68 tokens)

Every entity in a region, paged

The Bags That Pay register entities in one region (a state or a jurisdiction, by id or name), optionally for one service, 50 a page.

Input parameters:

- `page` (integer)
- `pageSize` (integer)
- `region` (string, required)
- `service` (string)

### `entities_export` (~70 tokens)

The whole register, in pages (access key required)

Every entity of Bags That Pay register, 200 a page, with provenance. Needs an access key (Authorization: Bearer); export pages are metered per key per day. Without a key the answer says how to get one.

Input parameters:

- `page` (integer)
- `pageSize` (integer)

### `listing_describe` (~45 tokens)

How listing on this directory works

What a listing on Bags That Pay is, what it costs, how it is paid, who publishes it, and every profile field it takes. Read this to the person first.

### `listing_terms` (~34 tokens)

The listing terms and the profile allowlist

The clauses a listing is judged by, their version (send it back as termsVersion), and every profile field the directory takes.

### `agent_session_start` (~53 tokens)

Start a wallet sign-in (Sign In With Solana)

Give a Solana address; get the exact message to sign. A signature, not a transaction: no fee, nothing moves. Then call agent_session_verify with the base64 signature.

Input parameters:

- `address` (string, required)

### `agent_session_verify` (~76 tokens)

Finish the wallet sign-in; receive the session token

The address, the exact message from agent_session_start and its base64 Ed25519 signature. Returns a session token to pass as `session` to every later call (valid 30 days, revocable from the account page).

Input parameters:

- `address` (string, required)
- `message` (string, required)
- `signature` (string, required)

### `claim_start` (~78 tokens)

Claim a register entry (proof of the register's own domain)

Names the entry (scheme + value, e.g. lei); returns the proof domain the register lists and the token to place as a TXT record, a well-known file, or via a verified email there.

Input parameters:

- `scheme` (string, required)
- `session` (string, required): the session token from agent_session_verify
- `value` (string, required)

### `claim_verify` (~51 tokens)

Check a claim's proof now

The server reads DNS, the well-known file and the verified email; verified claims are badges on the profile.

Input parameters:

- `id` (string, required)
- `session` (string, required): the session token from agent_session_verify

### `claim_status` (~38 tokens)

My claims

Every claim of this account with its status and, while pending, the instructions.

Input parameters:

- `session` (string, required): the session token from agent_session_verify

### `listing_draft` (~152 tokens)

Draft a listing (validated against the terms before any money)

Creates a listing draft on Bags That Pay. Send the fullest profile you can (listing_describe lists the fields); a scam-shaped or off-list field is refused by name. Returns the listing id and status awaiting_payment.

Input parameters:

- `about` (string)
- `authorised` (boolean, required)
- `enquiryEmail` (string)
- `jurisdictions` (required): ISO codes
- `languages` (string)
- `name` (string, required)
- `profile` (object)
- `register` (object)
- `services` (required)
- `session` (string, required): the session token from agent_session_verify
- `termsAccepted` (boolean, required)
- `termsVersion` (string, required)
- `website` (string)

### `listing_pay_card` (~64 tokens)

Pay by card (hosted checkout for a human)

Returns a Stripe Checkout URL at the site's price. A human completes it in a browser; the site learns of payment from Stripe's verified event, never from the browser.

Input parameters:

- `id` (string, required)
- `session` (string, required): the session token from agent_session_verify

### `listing_pay_stripe` (~93 tokens)

Pay by Stripe without a browser (a payment method you hold)

Send a Stripe payment method id (pm_...) the agent is entitled to use; the server charges the SITE's price off-session. Answers succeeded (the listing enters review) or requires_action (use listing_pay_card for a human); never charges an amount you name.

Input parameters:

- `id` (string, required)
- `paymentMethod` (string, required)
- `session` (string, required): the session token from agent_session_verify

### `listing_pay_usdc` (~74 tokens)

Pay in USDC on Solana (automatic)

Returns the Solana Pay transfer request: recipient, exact amount, USDC mint and a unique reference. Pay it from the wallet (include the reference as a read-only key), then call listing_confirm_usdc.

Input parameters:

- `id` (string, required)
- `session` (string, required): the session token from agent_session_verify

### `listing_confirm_usdc` (~67 tokens)

Confirm the USDC payment from the chain

The SERVER finds the transfer by reference and reads the treasury's balance change; a short or wrong-token transfer is reported by name and not credited. On success the listing enters review.

Input parameters:

- `id` (string, required)
- `session` (string, required): the session token from agent_session_verify

### `listing_status` (~46 tokens)

My listings

Every listing of this account with its status (awaiting_payment, pending_review, published, refused, withdrawn, expired).

Input parameters:

- `session` (string, required): the session token from agent_session_verify

### `listing_withdraw` (~38 tokens)

Withdraw a listing

Takes down a listing of this account.

Input parameters:

- `id` (string, required)
- `session` (string, required): the session token from agent_session_verify

### `listings_published` (~43 tokens)

Published listings

What firms have added on top of the register (published rows only), optionally for one register entry.

Input parameters:

- `scheme` (string)
- `value` (string)

### `placements_active` (~51 tokens)

Active sponsored placements on a page

The Sponsored slot's contents for a page (home | region | leaf); labelled as sponsored in the answer.

Input parameters:

- `leaf` (string)
- `page` (string, required)
- `region` (string)

### `claim_public` (~40 tokens)

Is a register entry claimed?

Whether an entry has a verified claim, by which proof and when — never by whom.

Input parameters:

- `scheme` (string, required)
- `value` (string, required)

### `enquiry_describe` (~69 tokens)

What you get: an ENQUIRY with a human (not a purchase, not a guaranteed quote)

Read first. States plainly what submit_enquiry does on Bags That Pay: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the details, the consent wording, and how the person confirms.

### `enquiry_fields` (~48 tokens)

The questions the enquiry asks

Every field of the Bags That Pay enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.

### `submit_enquiry` (~225 tokens)

Submit an ENQUIRY to human providers (two steps; not a purchase)

Submits an enquiry to Bags That Pay — NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token — show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "By submitting you agree Bags That Pay passes your question to the issuer or data provider you asked about."

Input parameters:

- `answers` (object, required): the person's answers, keyed by field key
- `confirmation` (string): the confirmation token from step 1, after the person has approved the summary
- `consent` (boolean, required): true only when the person has agreed to: By submitting you agree Bags That Pay passes your question to the issuer or data provider you asked about.

## Diagnostics

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

## Score history

- 2026-09-20: 67
- 2026-09-19: 66
- 2026-09-18: 66
- 2026-09-17: 66
- 2026-09-16: 65
- 2026-09-15: 65
- 2026-09-14: 64
- 2026-09-13: 64
- 2026-09-12: 63

## Common questions

### What is the com.bagsthatpay/site MCP server?

com.bagsthatpay/site is an MCP server listed in the public MCP registry as com.bagsthatpay/site. Bags That Pay: the site's own MCP server, dataset, enquiry, entities, listing (enquiry = a... This page covers its hosted endpoint (https://bagsthatpay.com/mcp).

### Is the com.bagsthatpay/site MCP server safe to use?

com.bagsthatpay/site scores 67 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 com.bagsthatpay/site MCP server expose?

com.bagsthatpay/site exposes 32 tools: dataset_columns, dataset_search, dataset_row, dataset_compare, dataset_stats, and 27 more. Their descriptions and schemas cost roughly 2,076 tokens of context every time the server is loaded.

### Does the com.bagsthatpay/site MCP server require authentication?

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

### Is the com.bagsthatpay/site MCP server still maintained?

com.bagsthatpay/site is still listed as active in the MCP registry. We last reached this channel on 20 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://bagsthatpay.com/mcp
- Repository: https://github.com/joeetdev/venture-estate
- Website: https://bagsthatpay.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-bagsthatpay-site/bagsthatpay.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-bagsthatpay-site/bagsthatpay.json
- HTML version of this page: https://verifymcp.io/servers/com-bagsthatpay-site/bagsthatpay