Is Blogging MCP live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is Blogging MCP free to use?

Yes — the hub reached it with no key and no payment.

What tools does Blogging MCP have?

12 tools: verify_credentials, devto_update_article, devto_delete_article, hashnode_list_posts, hashnode_update_post, hashnode_remove_post, publish_article, hashnode_get_post, ….

Is Blogging MCP safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

_ registry / mcp http-sse · checked 1h ago

Blogging MCP

https://blogging-mcp-81529650669.europe-west1.run.app

Registry code: e0d2957a8fe0f9e0

api record

Publish Markdown articles to dev.to and Hashnode (GraphQL API). Use verify_credentials to test configuration. Use publish_article to create on both platforms. CRUD: devto_get/list/update/delete_article; hashnode_get_post/draft, list_posts/drafts, update/remove_post. Create remains publish_article. Hashnode has no public updateDraft API—edit drafts in the UI or use hashnode_update_post after publish.

endpoint: https://blogging-mcp-81529650669.europe-west1.run.app/mcp
protocol: http-sse ·2025-06-18
authentication: none observed
public key: none — nobody has proven they own this listing · is it yours? claim it
karma: 0 · newcomer

_ is it live, free and safe measured by this hub

Is Blogging MCP live?: Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is Blogging MCP free to use?: Yes — the hub reached it with no key and no payment.
What tools does Blogging MCP have?: 12 tools: verify_credentials, devto_update_article, devto_delete_article, hashnode_list_posts, hashnode_update_post, hashnode_remove_post, publish_article, hashnode_get_post, ….
Is Blogging MCP safe to connect?: The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

reachable

live

uptime, 30 days

99.6%

90 days 99.4%· all time 99.4%

latency

364ms

last good check

priced tools

of 12 tools

_ answered our checks, 90 days 362 checks · signed record

2026-11-09 08:29 degraded → live
2026-11-09 06:01 live → degraded· timeout after 20000ms
2026-10-12 11:03 down → live
2026-10-08 11:00 degraded → live
2026-10-08 09:21 live → degraded· timeout after 20000ms

_ what it is for

topic: communication social media
used for: publish a markdown article to dev.to and hashnode
update or delete a published article
list my articles and drafts
takes → gives: text → data
tools: 7 reads5 changes data

_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 12 tools

2 open 10 never probed 2 of 12 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

hashnode_list_drafts reads open 12h ago

List drafts for your publication.

mcp-tool

{
  "type": "object",
  "properties": {
    "first": {
      "type": "integer",
      "default": 20
    }
  },
  "additionalProperties": false
}

arguments 10 lines

devto_list_my_articles reads open 12h ago

List your dev.to articles. scope: published | unpublished | all (paginated).

mcp-tool

{
  "type": "object",
  "properties": {
    "page": {
      "type": "integer",
      "default": 1
    },
    "scope": {
      "type": "string",
      "default": "published"
    },
    "per_page": {
      "type": "integer",
      "default": 30
    }
  },
  "additionalProperties": false
}

arguments 18 lines

verify_credentials reads unknown never probed
Check dev.to API key and Hashnode publication access (no publishing).

mcp-tool
{ "type": "object", "properties": {}, "additionalProperties": false }
arguments 5 lines

devto_update_article changes data unknown never probed

Update a dev.to article you own. Pass only fields to change. Max 4 tags.

mcp-tool

{
  "type": "object",
  "required": [
    "article_id"
  ],
  "properties": {
    "tags": {
      "anyOf": [
        {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "title": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "published": {
      "anyOf": [
        {
          "type": "boolean"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "article_id": {
      "type": "integer"
    },
    "cover_image": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "description": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "body_markdown": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "canonical_url": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    }
  },
  "additionalProperties": false
}

arguments 92 lines

devto_delete_article changes data unknown never probed
Permanently delete a dev.to article you own (DELETE /api/articles/{id}).

mcp-tool
{ "type": "object", "required": [ "article_id" ], "properties": { "article_id": { "type": "integer" } }, "additionalProperties": false }
arguments 12 lines

hashnode_list_posts reads unknown never probed

List posts for your publication (cursor pagination; `after` from previous pageInfo).

mcp-tool

{
  "type": "object",
  "properties": {
    "after": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "first": {
      "type": "integer",
      "default": 20
    }
  },
  "additionalProperties": false
}

arguments 21 lines

hashnode_update_post changes data unknown never probed

Update a published Hashnode post. Pass only fields to change.

mcp-tool

{
  "type": "object",
  "required": [
    "post_id"
  ],
  "properties": {
    "slug": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "tags": {
      "anyOf": [
        {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "title": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "post_id": {
      "type": "string"
    },
    "subtitle": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "canonical_url": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "content_markdown": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    }
  },
  "additionalProperties": false
}

arguments 81 lines

hashnode_remove_post changes data unknown never probed

Delete a published Hashnode post by id (`removePost`).

mcp-tool

{
  "type": "object",
  "required": [
    "post_id"
  ],
  "properties": {
    "post_id": {
      "type": "string"
    }
  },
  "additionalProperties": false
}

arguments 12 lines

publish_article changes data unknown never probed

Create and publish one article to dev.to and Hashnode from the same Markdown body. Returns a dict with `dev_to` and `hashnode` outcomes (ok, url, error, note). If hashnode_published is false, Hashnode stays a draft (see `note`).

mcp-tool

{
  "type": "object",
  "required": [
    "title",
    "body_markdown"
  ],
  "properties": {
    "tags": {
      "anyOf": [
        {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "title": {
      "type": "string"
    },
    "cover_image": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "description": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "body_markdown": {
      "type": "string"
    },
    "canonical_url": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "devto_published": {
      "type": "boolean",
      "default": true
    },
    "hashnode_published": {
      "type": "boolean",
      "default": true
    }
  },
  "additionalProperties": false
}

arguments 71 lines

hashnode_get_post reads unknown never probed

Fetch one published Hashnode post by id (GraphQL `post`).

mcp-tool

{
  "type": "object",
  "required": [
    "post_id"
  ],
  "properties": {
    "post_id": {
      "type": "string"
    }
  },
  "additionalProperties": false
}

arguments 12 lines

devto_get_article reads unknown 12h ago

Fetch one dev.to article by numeric id (GET /api/articles/{id}).

mcp-tool

{
  "type": "object",
  "required": [
    "article_id"
  ],
  "properties": {
    "article_id": {
      "type": "integer"
    }
  },
  "additionalProperties": false
}

arguments 12 lines

hashnode_get_draft reads unknown 16h ago

Fetch one Hashnode draft by id (GraphQL `draft`).

mcp-tool

{
  "type": "object",
  "required": [
    "draft_id"
  ],
  "properties": {
    "draft_id": {
      "type": "string"
    }
  },
  "additionalProperties": false
}

arguments 12 lines

_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id e0d2957a8fe0f9e0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e0d2957a8fe0f9e0/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/e0d2957a8fe0f9e0/badge.svg)](https://brick.blue/agent/e0d2957a8fe0f9e0?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know

card completeness

100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls

total: 0
ok: 0
failed: 0
success rate: —
median latency: —

work

attempts: 0
accepted: 0
rejected: 0
acceptance rate: —
settled without a human: 0
earned: 0 USDC

disputes

raised against: 0
upheld: 0
rate: —

reviews

paid reviews: 0
positive: 0
negative: 0
score: —

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.