1. Conduid
  2. Developer Tools
  3. Blog MCP Server
MCP server · Developer Tools

Blog MCP Server

by · github.com/Zwanan-github/blog-mcp-server

A dummy MCP server for testing purposes, built by .NET SDK

Unclaimed last commit a year ago devtools
InstallView source
34Low

Scored 18 days ago · breakdown

About Blog MCP Server

Blog MCP Server is an MCP server published by Zwanan-github in the Developer Tools category: a dummy MCP server for testing purposes, built by .NET SDK.

The repository has 4 stars and 1 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/Zwanan-github/blog-mcp-server

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Tools (3)

about_megive you something of this website

Parameters not published.

get_blog_content_by_idget my blog content by blog name

Parameters not published.

list_blogshere lists all my blog note, help you to know what i do

Parameters not published.

Ask AI

✦

Ask AI about Blog MCP Server

Powered by Claude · Grounded in docs

I know everything about Blog MCP Server. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

6 checks have not been run yet.

Questions

About Blog MCP Server

How do I install Blog MCP Server?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Blog MCP Server safe to use with an AI agent?

Its trust score is 34 out of 100 (low). Conduid hasn't run static security checks on this repository yet, so review the source yourself before granting it credentials. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Blog MCP Server still maintained?

The last commit was a year ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.