# Pugi (remote · api.pugi.io)

AI product team: builds and publishes websites from a brief, logos, security checks.

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

## Components

- remote · `api.pugi.io`: 83/100 (this document), [markdown](https://verifymcp.io/servers/io-pugi-pugi/api-agent-v1-mcp.md), [page](https://verifymcp.io/servers/io-pugi-pugi/api-agent-v1-mcp)

## Channel facts

- Endpoint: `https://api.pugi.io/api/agent/v1/mcp`
- Transports: `streamable-http`
- Auth: `required`
- 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**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - 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.
  - 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**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 41/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 4245 tokens (~169/item across 25 items; 15 tools + 10 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 93% of tool parameters carry a description.
- **Tool Safety**: 88/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 1 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "publish_status" implies "publish" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 17 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.
  - Supports UI / widget rendering.

## Install

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

Pugi is a hosted endpoint at https://api.pugi.io/api/agent/v1/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 io-pugi-pugi 'https://api.pugi.io/api/agent/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-pugi-pugi": {
      "url": "https://api.pugi.io/api/agent/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-pugi-pugi": {
      "type": "http",
      "url": "https://api.pugi.io/api/agent/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-pugi-pugi]
url = "https://api.pugi.io/api/agent/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-pugi-pugi": {
      "type": "remote",
      "url": "https://api.pugi.io/api/agent/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-pugi-pugi --url 'https://api.pugi.io/api/agent/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-pugi-pugi:
    url: "https://api.pugi.io/api/agent/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-pugi-pugi": {
      "Transport": "http",
      "Url": "https://api.pugi.io/api/agent/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-pugi-pugi -t streamable-http -u 'https://api.pugi.io/api/agent/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-pugi-pugi": {
      "type": "http",
      "url": "https://api.pugi.io/api/agent/v1/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 83, +1)

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

### 2026-11-19 (score 82, +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-11-17 (score 81, +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-11-15 (score 80, +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-11-12 (score 79, +1)

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

### 2026-11-10 (score 78, +1)

- [security] Resource “Pugi build” now points somewhere else: ui://pugi/build.7d348bdfe3c7.html → ui://pugi/build.f0f4e113cddc.html
- [security] Resource “Pugi build (ChatGPT compatibility)” now points somewhere else: ui://pugi/build.7d348bdfe3c7.skybridge.html → ui://pugi/build.f0f4e113cddc.skybridge.html
- [security] Resource “Pugi logos” now points somewhere else: ui://pugi/logos.4ab7be0c3e48.html → ui://pugi/logos.b52a5853abdb.html
- [security] Resource “Pugi logos (ChatGPT compatibility)” now points somewhere else: ui://pugi/logos.4ab7be0c3e48.skybridge.html → ui://pugi/logos.b52a5853abdb.skybridge.html
- [security] Resource “Pugi published” now points somewhere else: ui://pugi/published.019ed6e0538b.html → ui://pugi/published.8b49bfbd4f7a.html
- [security] Resource “Pugi published (ChatGPT compatibility)” now points somewhere else: ui://pugi/published.019ed6e0538b.skybridge.html → ui://pugi/published.8b49bfbd4f7a.skybridge.html
- [security] Resource “Pugi repository” now points somewhere else: ui://pugi/repository.a2ede09cf410.html → ui://pugi/repository.2beed3ab1e1f.html
- [security] Resource “Pugi repository (ChatGPT compatibility)” now points somewhere else: ui://pugi/repository.a2ede09cf410.skybridge.html → ui://pugi/repository.2beed3ab1e1f.skybridge.html
- [security] Resource “Pugi website” now points somewhere else: ui://pugi/website.6c4b91304767.html → ui://pugi/website.e11fbb453013.html
- [security] Resource “Pugi website (ChatGPT compatibility)” now points somewhere else: ui://pugi/website.6c4b91304767.skybridge.html → ui://pugi/website.e11fbb453013.skybridge.html

### 2026-11-08 (score 77, +1)

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

### 2026-11-06 (score 76, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (15)

### `get_balance` (~32 tokens)

Get credit balance

Use this when the person asks about their Pugi plan, credit or what they spent today. Free and read-only.

### `buy_credits_link` (~57 tokens)

Get a link to add credit

Get a link to add credit.

Input parameters:

- `amount_usd` (number): How much credit to add. Rounded up to a pack of 5, 10, 25, 50 or 100 USD. Default 5.

### `scan_url` (~134 tokens)

Check a website for security issues

Use this when the person wants a public website checked for security problems, for example "is my site secure?" or "check example.com". Free and read-only: HTTPS, security headers, cookie flags and exposed keys, with a grade from A+ to F and how to fix each finding. Not a pentest. Do not use for private or local addresses or for code repositories (use scan_repo).

Input parameters:

- `language` (string): The language the person is writing in, as a BCP 47 tag such as "ru".
- `url` (string, required): The public address to check, for example https://example.com

### `make_logo` (~856 tokens)

Make four logos

Use this when the person wants a logo or brand mark for a business, shop, product or project, for example "make a logo for Blue Fern Bakery". business_name must be the name the person gave, in their own words. If they gave no name, do not call this tool: ask them what the company is called, in their language (in Russian: «Как называется компания?»); never invent or translate a name. Pass their description and their own style words verbatim (never add style, colour or mood words yourself), and language (the language they write in). After a call, never describe what you passed to Pugi, name the tool or promise logos while a question is open; never say you passed something without calling. Pugi first asks the person to confirm the name in the card, once per name. If they say yes in words, call this tool again with the same business_name and the question_token. If they give another name in words, call this tool again with that business_name. A new business name is a new brand: never reuse another business's logo or answers. Pugi runs the same short brand interview as logo.pugi.io, one question per call (status needs_input), shown with its options in the card: tell the person in one short line to answer there or in their own words, without listing the options, then call again with their answer (trade for the first question, answers for the later ones). Use draw_now true only when the person says to draw now. Then it draws four whole logo options (PNG) the person can pick, change and use on a Pugi website. Generates logo design assets only. Do not use for photos, illustrations, posters, memes or editing an image the person uploaded; to change logos already shown in this conversation use refine_logo.

Input parameters:

- `answers` (array): Only after Pugi asked (status needs_input): every answer so far to its interview questions, the id Pugi gave and the user's words verbatim.
- `business_name` (string): The business name, as written by the user.
- `colours`: Optional. Hex colours: {"primary": "#1e3a8a", "secondary": "#f59e0b", "text": "#111827"}, or a list of one to three of them in that order.
- `description` (string): The user’s description verbatim, including location, imagery and mood.
- `draw_now` (boolean): True when the user wants the logos drawn now, without more questions.
- `idempotency_key` (string, required): A unique string for this call, reused only to retry it. The same key with the same arguments is never charged twice.
- `industry` (string): Optional. What the business does, for example "coffee shop" or "accounting firm".
- `language` (string): The language the user is writing to you in, as a BCP 47 tag such as "uk", "de" or "pt-BR"; the questions come back in it.
- `name` (string)
- `name_proof` (string): Set by Pugi's card when the person confirms the name. Leave it out.
- `niche` (string)
- `palette` (string)
- `question_token` (string): Only after Pugi asked (status needs_input): the question_token it returned. Pass it with the trade, the answers or draw_now; without it the brief starts again.
- `read_state` (boolean): Only with question_token: read what the logo card shows now (the drawn logos with their logo_id, or that the person is still answering). It only reads: it answers nothing for the person, draws nothin…
- `refine_notes` (string)
- `refines` (array)
- `style` (string): Style words verbatim; styles also accepts a list.
- `styles` (array): The user’s style words verbatim.
- `tagline` (string)
- `trade` (string): Only after Pugi asked (status needs_input): the slug the user picked from the options, for example "coffee-shop", or their own words.

### `publish_status` (~64 tokens)

Get publish status

Use this when the person asks which of their Pugi sites are live and at what address.

Input parameters:

- `language` (string): The language the person is writing in, as a BCP 47 tag such as "ru".
- `project_id` (string): Optional project id.

### `my_sites` (~56 tokens)

List my sites

Use this when the person refers to a site or app they built earlier (in this chat or another one) and you need its project_id, for example to publish it. Call it before offering to build again. Free and read-only.

### `catalog_search` (~174 tokens)

Search the Pugi catalogue

Use this when the person wants ideas or a starting point for a site or app, for example "show me bakery websites". Free. Returns sites and apps people built with Pugi; if none matches it returns the nearest category and says so (match: nearest_category), so tell the person they are the nearest. Each has a brief and the tool to start a similar project in this chat (build_with). It does not copy anyone's code.

Input parameters:

- `category` (string): Optional category.
- `limit` (integer): How many cards to return. Default 10.
- `query` (string): Optional words for what the person wants, in any language, for example "booking" or "coffee shop".
- `tags` (array): Optional tags; a card must carry every one, for example ["saas"].

### `scan_repo` (~177 tokens)

Check a GitHub repository for security issues

Use this when the person wants a public GitHub repository checked for leaked secrets, vulnerable or malicious dependencies and risky code. No code is run. 3 free checks a day per account, then $1 when the check finishes; a failed check costs nothing. Do not use for websites (use scan_url) or private repositories.

Input parameters:

- `idempotency_key` (string, required): A unique string naming this check. Reuse it to collect the result or to retry; the same key is never charged twice.
- `language` (string): The language the person is writing in, as a BCP 47 tag such as "ru".
- `ref` (string): Optional branch name. Default: the repository's default branch.
- `repo_url` (string, required): A public GitHub repository, for example https://github.com/owner/repo

### `build_app` (~518 tokens)

Build a web app

Use this when the person wants something people use: upload a photo, generate or transform pictures with AI, accounts or sign-in, saved data, a tool, a calculator, a game, bookings, a dashboard. Pass their request as they said it; never turn it into a landing page. An app that makes pictures with AI asks for the owner's own image-AI key; it never fakes results. Pass the customer's brief in the customer's own words; do not add features the customer did not ask for (no invented sign-up, accounts, subscriptions or payments). When it is built Pugi checks it for security issues, and publish waits for that check. An app that needs a server or a database moves onto Pugi's servers on its own; the person stays in this chat. In hosts that render the build card (MCP Apps or ChatGPT widget), the card tracks progress automatically: do not poll job_status. In hosts without a build card (Claude Code or API), call job_status with the job_id until the job is finished, stopped or failed. Do not use for a simple website (use build_site) or to change an app already built here (use edit).

Input parameters:

- `brandHandoffId` (string): BrandHandoff from logo.pugi.io.
- `brief` (string, required): The app to build, in the customer's own words.
- `brief_confirmed` (boolean): True only after the person has seen the summary and agreed. In a chat, without it nothing starts and the summary comes back.
- `brief_version` (string): With brief_confirmed: the version of the summary the person agreed to, as returned with that summary.
- `idempotency_key` (string, required): A unique string naming this build. Reuse it only to retry the same call; it is never charged twice.
- `language` (string): The language the person is writing in, as a BCP 47 tag such as "ru".
- `locale` (string): Site language (legacy alias for site_language).
- `logo_id` (string): Selected logo_id returned by make_logo.
- `max_usd` (number): The most this build may cost in USD (default 5).
- `pick` (string): Console gallery starter slug.
- `site_language` (string): Language for the app content; independent of the chat card language.
- `theme` (string): Console theme slug.
- `without_logo` (boolean): True only when the person said this site should not use the logo they picked.

### `build_site` (~526 tokens)

Build a website

For a business's marketing site only, for example "a site for my bakery". Something people use (upload a photo, AI pictures, sign-in, a tool, a game) is an app: use build_app, never a landing page. Pass the customer's brief in the customer's own words; do not add features the customer did not ask for (no invented sign-up, accounts, subscriptions or payments). First call: nothing starts, a summary returns; after a yes, call with its action.arguments. In hosts that render the build card (MCP Apps or ChatGPT widget), the card tracks progress automatically: do not poll job_status. In hosts without a build card (Claude Code or API), call job_status with the job_id until the job is finished, stopped or failed. Not for changing a built site (use edit).

Input parameters:

- `as_site` (boolean): True only when Pugi said this sounds like an app (app_suggested) and the person chose a marketing website anyway.
- `brandHandoffId` (string): BrandHandoff from logo.pugi.io.
- `brief` (string, required): The customer's request in their own words: what the site is for and any pages, texts, colours or style they named. Do not add features they did not ask for.
- `brief_confirmed` (boolean): True only after the person has seen the summary and agreed. In a chat, without it nothing starts and the summary comes back.
- `brief_version` (string): With brief_confirmed: the version of the summary the person agreed to, as returned with that summary.
- `idempotency_key` (string, required): A unique string naming this job. The same key returns the same job and is never charged twice.
- `language` (string): The language the person is writing in, as a BCP 47 tag such as "ru".
- `locale` (string): Site language (legacy alias for site_language).
- `logo_id` (string): Selected logo_id returned by make_logo.
- `max_usd` (number): The run ceiling in USD; plan builds are included in the subscription. For credit builds, the most this build may cost. Default 5. Credit accounts pay actual cost, usually less.
- `pick` (string): Console gallery starter slug.
- `site_language` (string): Language for the website content; independent of the chat card language.
- `theme` (string): Console theme slug.
- `without_logo` (boolean): True only when the person said this site should not use the logo they picked.

### `edit` (~476 tokens)

Change a site Pugi built

Use this when the person asks to change a Pugi website or app from this conversation: "change the headline", "make the buttons green", "add a menu page". Pass the change in the customer's own words; do not add features the customer did not ask for (no invented sign-up, accounts, subscriptions or payments). Pass the job_id or project_id from the last build result. Do not use to start a new site or app. In hosts that render the build card (MCP Apps or ChatGPT widget), the card tracks progress automatically: do not poll job_status. In hosts without a build card (Claude Code or API), call job_status with the job_id until the job is finished, stopped or failed.

Input parameters:

- `brandHandoffId` (string): BrandHandoff from logo.pugi.io.
- `brief_confirmed` (boolean): True only after the person has seen the summary and agreed. In a chat, without it nothing starts and the summary comes back.
- `brief_version` (string): With brief_confirmed: the version of the summary the person agreed to, as returned with that summary.
- `idempotency_key` (string, required): A unique string naming this job. The same key returns the same job and is never charged twice.
- `instruction` (string, required): The change to make, in plain words.
- `job_id` (string): The job_id of the build (or of an earlier edit) of the site to change.
- `language` (string): The language the person is writing in, as a BCP 47 tag such as "ru".
- `locale` (string): Site language (legacy alias for site_language).
- `logo_id` (string): Selected logo_id returned by make_logo.
- `max_usd` (number): The run ceiling in USD; plan edits are included in the subscription. For credit edits, the most this change may cost. Default 2.
- `pick` (string): Console gallery starter slug.
- `project_id` (string): Or the project_id of that site.
- `site_language` (string): Language for the website content; independent of the chat card language.
- `theme` (string): Console theme slug.
- `without_logo` (boolean): True only when the person said this site should not use the logo they picked.

### `job_status` (~122 tokens)

Get the status of a build

Use this when the person asks how a Pugi build or change is going, or for a fresh preview link. In hosts that render the build card (MCP Apps or ChatGPT widget), the card tracks progress automatically: do not poll job_status. In hosts without a build card (Claude Code or API), call job_status with the job_id until the job is finished, stopped or failed. Preview links expire after 15 minutes; call again for a fresh link.

Input parameters:

- `job_id` (string, required): The job_id build_site, build_app or edit returned.

### `publish` (~177 tokens)

Publish a built site

Use this when the person asks to put a Pugi website or app live ("publish", "go live"). Free. Puts the latest version on its pugi.app address after the security check every Pugi publish runs; publishing again replaces the live version.

Input parameters:

- `idempotency_key` (string): Optional. Reuse it to retry the same publish.
- `job_id` (string): The job_id of the build (or the latest edit) to publish.
- `language` (string): The language the person is writing in, as a BCP 47 tag such as "ru".
- `project_id` (string): Or the project_id of that site.
- `publish_with_samples` (boolean): Only after the person saw the list of sample details this tool answered with (sample_facts_remain) and chose to keep them.

### `select_logo` (~130 tokens)

Keep a logo

Use this when the person picks one of the Pugi logos shown in this conversation (in the card or in words, such as "the second one"). Saves that logo for their business and returns the summary a website or app will be built from: show it and wait. Call again with correction when they change anything in the summary. Draws and buys nothing.

Input parameters:

- `correction` (string): The person's correction to the summary, in their own words.
- `language` (string): The person's language.
- `logo_id` (string, required): The logo_id of the picked logo, from the last logo result.

### `refine_logo` (~250 tokens)

Change the logos

Use this when the person asks to change Pugi logos already shown in this conversation: other colours, a calmer or bolder mood, another icon or font, "like the second one but blue". Draws four new options from the same brief with that change, without asking anything; it does not edit one chosen design. Pass exactly one of logo_id (from the last logo result) or question_token (from the logo card). Do not use for a different business name (use make_logo).

Input parameters:

- `change` (string, required): The change in the person's own words, for example "make it blue and calmer".
- `idempotency_key` (string, required): A unique string for this call, reused only to retry it.
- `language` (string): The language the person writes in, as a BCP 47 tag such as "ru".
- `logo_id` (string): The logo_id of one of the logos to change, from the last logo result (the picked one when there is one). Leave it out when you pass question_token.
- `question_token` (string): The question_token of the logo card, when you have no logo_id. Leave it out when you pass logo_id.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-pugi-pugi/api-agent-v1-mcp#diagnostics

## Score history

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

## Common questions

### What is the Pugi MCP server?

Pugi is an MCP server listed in the public MCP registry as io.pugi/pugi. AI product team: builds and publishes websites from a brief, logos, security checks. This page covers its hosted endpoint (https://api.pugi.io/api/agent/v1/mcp).

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

Pugi scores 83 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 Pugi MCP server expose?

Pugi exposes 15 tools: get_balance, buy_credits_link, scan_url, make_logo, publish_status, and 10 more. Their descriptions and schemas cost roughly 3,749 tokens of context every time the server is loaded.

### Does the Pugi MCP server require authentication?

Yes. Pugi 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 Pugi MCP server still maintained?

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

VerifyMCP ran 14 checks on Pugi, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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://api.pugi.io/api/agent/v1/mcp
- Website: https://pugi.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-pugi-pugi/api-agent-v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-pugi-pugi/api-agent-v1-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-pugi-pugi/api-agent-v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-pugi-pugi/api-agent-v1-mcp
