Journalize

io.github.chris-bsnPublished by GitHub account chris-bsnv1.0.1Updated Oct 24, 2026

Deprecated - moved to dev.journalize/journalize

The publisher's own server: Journalize

VerifiedStreamable HTTPWeb executable

Overview

AI-generated overview

A remote MCP endpoint at journalize.dev that has been deprecated and moved to a different registry identifier.

What you can do
The registry entry provides no tool list, README, or capability description. Its only stated content is that it is deprecated and has been moved to dev.journalize/journalize. No functions, resources, or prompts are documented here.
When to use it
Not recommended for new installations, since the entry is marked deprecated and superseded by another identifier. Anyone who previously used this endpoint should look for the replacement listing instead.
Requirements
It is declared as a remote streamable HTTP endpoint at journalize.dev with no packages, environment variables, or headers. No authentication is declared, though the actual service may still require it.
Before you install
The listing is deprecated and points to a different identifier, so configuration against this endpoint may stop working. No tools, permissions, or data handling are documented, so what the server can read or change cannot be assessed from this entry.

Installation

In SourceWeft

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

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.chris-bsn%2Fjournalize/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "journalize": {
      "type": "http",
      "url": "https://journalize.dev/mcp-deprecated-do-not-use"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Journalize integrations