MyOG Checker

social.myogPublished by myog.socialv0.1.1Updated Oct 24, 2026

Check a public page's static Open Graph and Twitter metadata locally. No account or API key.

VerifiedSTDIODesktop onlyWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

Checks a public web page's static Open Graph and Twitter metadata locally, without an account or API key.

What you can do
MyOG Checker runs as a local MCP server that inspects a public page's static Open Graph and Twitter card metadata. It fetches the page and reports the metadata tags it finds so an assistant can review how the link would appear when shared. No account or API key is required.
When to use it
Useful when you want to verify or debug the social sharing metadata of a page before publishing or sharing a link. It fits quick checks of Open Graph and Twitter card tags from within an assistant session.
Requirements
Runs as a local process on the user's machine, installed from the npm package myog-checker and started with npm. Desktop only; no web executable. No account, API key, environment variables, or headers are declared. Network access is needed to reach the public page being checked.
Before you install
The server fetches public pages over the network, so the URLs you give it are sent to those sites. It only reads static metadata; it does not log in or change anything on the target page.

Installation

In SourceWeft

  1. Open MyOG Checker in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestOct 15, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.