Blog2Social - Social Media Publishing
REMOTE · API.BLOG2SOCIAL.COM
Connect AI agents to Blog2Social and automate social media content workflows via MCP.
Available components
Last scanned (12 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (connections.remove). See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1316 tokens (~131/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management61
- Stability check failed: schema churn in the 30 days we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 5 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 0
- Tool “posts.insights” rewrote its description, which is the text the model reads security
- Tool “posts.insights” changed its title: Retrieve published post performance insights → Retrieve own published post performance insights cosmetic
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 58 to 61.
- 31 Oct 26 −2
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “posts.create” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “account.overview” rewrote its description, which is the text the model reads security
- Tool “connections.add” rewrote its description, which is the text the model reads security
- Tool “connections.list” rewrote its description, which is the text the model reads security
- Tool “connections.remove” rewrote its description, which is the text the model reads security
- Tool “credits.balance” rewrote its description, which is the text the model reads security
- Tool “networks.list” rewrote its description, which is the text the model reads security
- Tool “networks.properties” rewrote its description, which is the text the model reads security
- Tool “posts.insights” rewrote its description, which is the text the model reads security
- Tool “videos.status” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- New tool “posts.publish_post” functional
- Tool “account.overview” changed its title: Get account usage overview → Retrieve account usage overview cosmetic
- Tool “connections.add” changed its title: Start connecting a social account → Connect a social media account cosmetic
- Tool “connections.list” changed its title: List connected social accounts → List connected social media accounts cosmetic
- Tool “connections.remove” changed its title: Disconnect a connected social account → Disconnect a connected social media account cosmetic
- Tool “credits.balance” changed its title: Check the Blog2Social API credit balance → Check available Blog2Social API credits cosmetic
- Tool “networks.list” changed its title: List networks available to connect → List available social networks cosmetic
- Tool “networks.properties” changed its title: Get posting requirements by network and account type → Get social network publishing requirements cosmetic
- Tool “posts.insights” changed its title: Get post performance insights → Retrieve published post performance insights cosmetic
- Tool “videos.status” changed its title: Check video post publishing status → Check video publishing status cosmetic
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67.
- 29 Oct 26 0
- Tool “posts.create” rewrote its description, which is the text the model reads security
- 28 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “posts.create” rewrote its description, which is the text the model reads security
- Schema quality: 792 → 918 ▼ functional
- New tool “posts.insights” functional
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.blog2social.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.blog2social.com | CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB | 14 Jan 2026 | 22 Jan 2027 | RSA 4096 | SHA256-RSA | 87bf534bc4ed8fc7153cba950557506 |
| SANs: *.blog2social.com, blog2social.com | ||||||
| CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US (CA) | CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US | 1 Feb 2010 | 18 Jan 2038 | RSA 4096 | SHA384-RSA | 1fd6d30fca3ca51a81bbc640e35032d |
| CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB (CA) | CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US | 22 Mar 2021 | 18 Jan 2038 | RSA 4096 | SHA384-RSA | d27fbbc1de359e5216ad6149586099c4 |
| CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB (CA) | CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB | 22 Mar 2021 | 21 Mar 2036 | RSA 3072 | SHA384-RSA | 397a66cc2756362e0daa87ca6eabe3b1 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.blog2social.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| blog2social.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.blog2social.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.blog2social.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
account.overview Retrieve account usage overview ~123
Use this tool when the user asks for an account-level overview of Blog2Social API credit usage. It returns the current credit balance and aggregated usage totals grouped by day, endpoint, and social network. The optional days parameter must be an integer between 1 and 30. If omitted, the endpoint default applies. The results describe aggregated account usage. They do not provide performance metrics or analytics for individual published social media posts. Use posts.insights for individual post performance.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Number of calendar days to include, from 1 to 30. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
No examples provided.
connections.add Connect a social media account ~161
Use this tool when the user wants to connect an account on a selected social network. It starts OAuth authorization and returns an auth_link that the user must open and approve. It requires network_id and network_type_id obtained from networks.list. network_type_id 0 means profile, 1 means page, and 2 means group. The connection is not complete until the user finishes authorization. Pinterest also requires an active custom app assigned to the API service.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Optional language for the authorization flow, for example en or de. |
| network_id | integer | yes | Social media network ID returned by the networks.list tool. |
| network_type_id | integer | yes | Connection type: 0 = profile, 1 = page, 2 = group. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
No examples provided.
connections.list List connected social media accounts ~77
Use this tool to retrieve the social media accounts connected to the authenticated Blog2Social user. It returns the network, account type, display name, and client_user_network_id for each connection. Use it to identify the correct connected account before publishing or disconnecting it. It does not list networks available for connection. Use networks.list for that purpose.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | – |
No examples provided.
connections.remove Disconnect a connected social media account ~89
Use this tool only when the user explicitly asks to disconnect a specific connected social media account. It removes the connection identified by client_user_network_id from the authenticated Blog2Social user. This is a destructive action. After disconnection, the account cannot be used for publishing until it is connected again through connections.add.
| Name | Type | Req | Description |
|---|---|---|---|
| client_user_network_id | integer | yes | Connected social media account ID returned by connections.list. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
No examples provided.
credits.balance Check available Blog2Social API credits ~86
Use this tool to retrieve the current credit balance of the authenticated Blog2Social API account. Use it when the user asks about available credits or before an action that may consume credits, such as publishing or retrieving post insights. It returns the current available credit balance. It does not provide individual post analytics, account usage statistics, or billing details. Publishing is not possible when the balance is zero.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
No examples provided.
networks.list List available social networks ~86
Use this tool to retrieve the social networks available to the authenticated Blog2Social API user. It returns network IDs and supported account types, including profiles, pages, and groups. Use it before connecting an account or when valid network IDs and account types are required. It does not list connected accounts or start authorization. Use connections.list to retrieve connected accounts and connections.add to start connecting an account.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | – |
No examples provided.
networks.properties Get social network publishing requirements ~84
Use this tool to retrieve publishing requirements and capabilities for a specific social network and account type. It returns available publishing formats and restrictions, such as supported media formats, video support, and character limits. Use it before publishing to check whether the requested content is supported. Requirements and capabilities vary by network and account type. This tool does not publish content or guarantee acceptance by the social network.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | – |
No examples provided.
posts.insights Retrieve own published post performance insights ~173
Use this tool when the user asks for performance metrics or analytics for your own published social media post. It retrieves the latest available performance insights and associated credit information for the specified published post. It requires the public publish_url returned after a successful posts.publish_post operation. It works only for supported social networks and account types with tracking enabled. Available metrics depend on the social network, account type, published post, tracking availability, and data returned by the endpoint. Not all metrics are available for every post or network. Report only metrics actually returned by the server. Do not interpret missing metrics as zero or invent unavailable performance data. The request may deduct credits according to the account and network pricing. Consider the credit cost before making the request.
| Name | Type | Req | Description |
|---|---|---|---|
| post_url | string | yes | Public URL of the published post whose insights should be retrieved. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
No examples provided.
posts.publish_post Publish a post immediately ~261
Use this tool when the user explicitly asks to publish social media content immediately. It publishes the supplied b2s_posts to the connected social media account identified by client_user_network_id. This action publishes content directly and does not create a draft or schedule a post for later publication. postFormat must be: - 0 for text or link - 1 for image - 2 for video Image and video posts require mediaObjects with the matching IMAGE or VIDEO type and a publicly accessible HTTP or HTTPS URL. Check networks.properties before publishing to verify the requirements for the selected network and account type. The response can include: - publish_url for retrieving post performance insights with posts.insights - video_token for checking video publication status with videos.status Evaluate all returned error fields, including b2s_error_code. Do not automatically retry uncertain publishing operations.
| Name | Type | Req | Description |
|---|---|---|---|
| b2s_posts | array | yes | One or more posts to publish to the selected account. Use postFormat 0 for text or links, 1 for images, and 2 for videos; image and video posts require mediaObjects. |
| client_user_network_id | integer | yes | Connected social media account ID returned by connections.list. All posts in b2s_posts are published to this account. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | – |
No examples provided.
videos.status Check video publishing status ~124
Use this tool after a video post has been submitted through posts.publish_post and the response contains a video_token. It checks whether video publication has finished and returns the status for each target account. Possible statuses: - pending - failed - successful The response may include a publish_url after successful publication. Use the video_token returned by posts.publish_post. If the status is pending, check again later. Do not retrieve post insights until successful publication has been confirmed and a publish_url is available.
| Name | Type | Req | Description |
|---|---|---|---|
| video_token | string | yes | Video token returned when the video upload was created. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Blog2Social - Social Media Publishing MCP server?
Blog2Social - Social Media Publishing is a hosted endpoint at https://api.blog2social.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.
remote · api.blog2social.com
claude mcp add --transport http adenion-blog2social-api-mcp 'https://api.blog2social.com/mcp'
What is the Blog2Social - Social Media Publishing MCP server?
Blog2Social - Social Media Publishing is an MCP server listed in the public MCP registry as io.github.Adenion/blog2social-api-mcp. Connect AI agents to Blog2Social and automate social media content workflows via MCP. This page covers its hosted endpoint (https://api.blog2social.com/mcp).
Is the Blog2Social - Social Media Publishing MCP server safe to use?
Blog2Social - Social Media Publishing scores 69 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 Blog2Social - Social Media Publishing MCP server expose?
Blog2Social - Social Media Publishing exposes 10 tools: networks.list, connections.list, networks.properties, connections.remove, connections.add, and 5 more. Their descriptions and schemas cost roughly 1,264 tokens of context every time the server is loaded.
Does the Blog2Social - Social Media Publishing MCP server require authentication?
No. We connected to Blog2Social - Social Media Publishing without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Blog2Social - Social Media Publishing MCP server still maintained?
Blog2Social - Social Media Publishing is still listed as active in the MCP registry. We last reached this channel on 5 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 Blog2Social - Social Media Publishing MCP server?
VerifyMCP ran 12 checks on Blog2Social - Social Media Publishing, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Blog2Social - Social Media Publishing: HTTPS. 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.