@remcp/remcp 0.1.1 → 0.1.3

package/public/support.html

@@ -8,7 +8,7 @@
   <title>Support · ReMCP</title>
   <meta name="description" content="Troubleshoot ReMCP sign-in, device pairing, agent connectivity and MCP authorization.">
   <link rel="preconnect" href="https://www.gstatic.com" crossorigin>
-  <link rel="stylesheet" href="/style.css?v=remcp-012">
+  <link rel="stylesheet" href="/style.css?v=remcp-013">
   <meta property="og:site_name" content="ReMCP">
   <meta property="og:image" content="https://remcp.delio24.com/assets/og-remcp.png">
   <link rel="icon" href="/favicon.ico" sizes="any">
@@ -28,22 +28,38 @@
     <img class="brand-mark" src="/android-chrome-192x192.png" width="30" height="30" alt="" aria-hidden="true">
     <span translate="no">ReMCP</span>
   </a>
-  <nav aria-label="Primary"><a href="/docs">Docs</a><a href="/docs#install">Install</a><a href="/docs#update">Update</a><a href="/security">Security</a><a href="/support" aria-current="page">Support</a></nav>
+  <nav aria-label="Primary"><a href="/docs">Docs</a><a href="/security">Security</a><a href="/support" aria-current="page">Support</a></nav>
 </header>
 <main id="main" class="doc-shell">
   <aside class="doc-nav" aria-label="Documentation"><a href="/docs">Setup</a><a href="/docs#install">Install</a><a href="/docs#update">Update</a><a href="/security">Security</a><a href="/support" aria-current="page">Support</a><a href="/privacy">Privacy</a><a href="/terms">Terms</a></aside>
   <article class="prose">
     <p class="eyebrow">Support</p>
-    <h1>Troubleshoot ReMCP.</h1>
-    <p>Most connection failures fall into one of three layers: account authentication, device pairing, or the local device agent.</p>
-<h2>Device shows offline</h2><p>Verify the ReMCP agent service is running and outbound HTTPS/WSS access to <code>remcp.delio24.com</code> is allowed. Re-pair the device if its credential was revoked.</p>
-<h2>OAuth does not complete</h2><p>Return to the authorization screen, sign in to the intended ReMCP account, review the requested access, and choose <strong>Authorize ReMCP Access</strong>.</p>
-<h2>MCP tool cannot run</h2><p>Confirm the target computer is online and use <code>list_devices</code> to obtain its current device id. Device tools require that id.</p>
-<h2>Pairing code expired</h2><p>Generate a new pairing command from the workspace. Pairing codes are intentionally short-lived and single-use.</p>
-<h2>Check the installed agent</h2><div class="code-row"><pre><code id="support-command-1">remcp --version
-remcp status</code></pre><button class="copy-button code-copy" type="button" data-copy="#support-command-1" aria-label="Copy command" aria-live="polite">Copy</button></div><p>If <code>remcp</code> is not found, repeat the <a href="/docs#install">install command</a>. The first npx invocation is temporary; <code>--install</code> creates the persistent CLI.</p>
-<h2>Update or repair</h2><div class="code-row"><pre><code id="support-command-2">remcp update</code></pre><button class="copy-button code-copy" type="button" data-copy="#support-command-2" aria-label="Copy command" aria-live="polite">Copy</button></div><p>This refreshes the published CLI and restarts the installed user service. For an already paired device whose service is missing, run <code>remcp install</code>.</p>
-<h2>Need deployment help?</h2><p>For a self-hosted deployment, contact the operator who provisioned your ReMCP instance and include the affected layer: sign-in, pairing, agent connectivity, or MCP authorization.</p>
+    <h1>Troubleshooting.</h1>
+    <p>Check the layer that is failing: sign-in, pairing, the local agent, or MCP authorization.</p>
+
+    <h2>Sign-in does not open</h2>
+    <p>Use <strong>Continue with Google</strong> or <strong>Continue with GitHub</strong>. ReMCP does not use email/password sign-in on the hosted site. If a popup is blocked, allow popups for <code>remcp.delio24.com</code> and try again.</p>
+
+    <h2>The <code>remcp</code> command is missing</h2>
+    <div class="copy-field"><code id="support-install">npm install --global @remcp/remcp@latest</code><button class="copy-icon-button" type="button" data-copy="#support-install" aria-label="Copy install command"><svg class="icon-copy" viewBox="0 0 24 24" aria-hidden="true"><rect x="9" y="9" width="11" height="11" rx="2"/><path d="M15 9V6a2 2 0 0 0-2-2H6a2 2 0 0 0-2 2v7a2 2 0 0 0 2 2h3"/></svg><svg class="icon-check" viewBox="0 0 24 24" aria-hidden="true"><path d="m5 12 4 4L19 6"/></svg></button></div>
+    <p>After installation, pair the computer from the signed-in workspace. The public install command alone does not pair a device.</p>
+
+    <h2>Pairing command expired</h2>
+    <p>Open the workspace and generate a new command. Each pairing command contains a one-time code and expires automatically.</p>
+
+    <h2>Device shows offline</h2>
+    <div class="copy-field"><code id="support-status">remcp status</code><button class="copy-icon-button" type="button" data-copy="#support-status" aria-label="Copy status command"><svg class="icon-copy" viewBox="0 0 24 24" aria-hidden="true"><rect x="9" y="9" width="11" height="11" rx="2"/><path d="M15 9V6a2 2 0 0 0-2-2H6a2 2 0 0 0-2 2v7a2 2 0 0 0 2 2h3"/></svg><svg class="icon-check" viewBox="0 0 24 24" aria-hidden="true"><path d="m5 12 4 4L19 6"/></svg></button></div>
+    <p>Confirm the user service is running and outbound HTTPS/WSS access to <code>remcp.delio24.com</code> is allowed. Re-pair only if the device credential was revoked or the local pairing state was removed.</p>
+
+    <h2>OAuth does not complete</h2>
+    <p>Return to the authorization page, sign in with the intended ReMCP account, review the requested scopes, and choose <strong>Authorize ReMCP Access</strong>.</p>
+
+    <h2>MCP tool cannot run</h2>
+    <p>Confirm the target device is online. A device tool needs the current ReMCP device id; clients can obtain it with <code>list_devices</code>.</p>
+
+    <h2>Update or repair</h2>
+    <div class="copy-field"><code id="support-update">remcp update</code><button class="copy-icon-button" type="button" data-copy="#support-update" aria-label="Copy update command"><svg class="icon-copy" viewBox="0 0 24 24" aria-hidden="true"><rect x="9" y="9" width="11" height="11" rx="2"/><path d="M15 9V6a2 2 0 0 0-2-2H6a2 2 0 0 0-2 2v7a2 2 0 0 0 2 2h3"/></svg><svg class="icon-check" viewBox="0 0 24 24" aria-hidden="true"><path d="m5 12 4 4L19 6"/></svg></button></div>
+    <p>If the CLI is paired but its background service is missing, run <code>remcp install</code>.</p>
   </article>
 </main>
 <footer class="site-footer">
@@ -51,9 +67,9 @@ remcp status</code></pre><button class="copy-button code-copy" type="button" dat
     <img class="brand-mark" src="/android-chrome-192x192.png" width="30" height="30" alt="" aria-hidden="true">
     <span translate="no">ReMCP</span>
   </div>
-  <nav aria-label="Footer"><a href="/docs">Docs</a><a href="/docs#install">Install</a><a href="/docs#update">Update</a><a href="/security">Security</a><a href="/support">Support</a><a href="/privacy">Privacy</a><a href="/terms">Terms</a></nav>
+  <nav aria-label="Footer"><a href="/docs">Docs</a><a href="/security">Security</a><a href="/support">Support</a><a href="/privacy">Privacy</a><a href="/terms">Terms</a></nav>
   <p>Open-source remote MCP infrastructure.</p>
 </footer>
-<script type="module" src="/copy.js?v=remcp-012"></script>
+<script type="module" src="/copy.js?v=remcp-013"></script>
 </body>
 </html>

package/public/terms.html

@@ -8,7 +8,7 @@
   <title>Terms of Service · ReMCP</title>
   <meta name="description" content="Terms for using the hosted ReMCP service and its remote-computer capabilities.">
   <link rel="preconnect" href="https://www.gstatic.com" crossorigin>
-  <link rel="stylesheet" href="/style.css?v=remcp-012">
+  <link rel="stylesheet" href="/style.css?v=remcp-013">
   <meta property="og:site_name" content="ReMCP">
   <meta property="og:image" content="https://remcp.delio24.com/assets/og-remcp.png">
   <link rel="icon" href="/favicon.ico" sizes="any">
@@ -28,24 +28,41 @@
     <img class="brand-mark" src="/android-chrome-192x192.png" width="30" height="30" alt="" aria-hidden="true">
     <span translate="no">ReMCP</span>
   </a>
-  <nav aria-label="Primary"><a href="/docs">Docs</a><a href="/docs#install">Install</a><a href="/docs#update">Update</a><a href="/security">Security</a><a href="/support">Support</a></nav>
+  <nav aria-label="Primary"><a href="/docs">Docs</a><a href="/security">Security</a><a href="/support">Support</a></nav>
 </header>
 <main id="main" class="doc-shell">
   <aside class="doc-nav" aria-label="Documentation"><a href="/docs">Setup</a><a href="/docs#install">Install</a><a href="/docs#update">Update</a><a href="/security">Security</a><a href="/support">Support</a><a href="/privacy">Privacy</a><a href="/terms" aria-current="page">Terms</a></aside>
   <article class="prose">
     <p class="eyebrow">Legal</p>
     <h1>Terms of Service</h1>
-    <p><strong>Effective September 16, 2026.</strong> These Terms apply to the hosted ReMCP service at remcp.delio24.com. The open-source software may also be self-hosted under its applicable software license.</p>
-<h2>Your account and devices</h2><p>You may connect only computers and accounts that you own or are authorized to administer. You are responsible for protecting your sign-in account, reviewing paired devices, and revoking devices or OAuth grants you no longer trust.</p>
-<h2>Remote actions</h2><p>ReMCP can expose powerful local operations, including reading and modifying files and starting or terminating processes. Some actions can be destructive or can affect external systems when a command run on your computer reaches them. You are responsible for reviewing and authorizing requested actions and for maintaining appropriate backups and operating-system permissions.</p>
-<h2>Acceptable use</h2><p>You may not use ReMCP to access systems without authorization, distribute malware, evade security controls, interfere with other users, conduct credential theft, or violate applicable law or third-party rights. You may not attempt to access devices belonging to another ReMCP account.</p>
-<h2>Service operation</h2><p>The hosted service may be updated, rate-limited, suspended or discontinued to protect users, respond to abuse, maintain security or operate the service. ReMCP does not guarantee uninterrupted availability. Self-hosted deployments are operated and secured by their administrators.</p>
-<h2>Third-party services and software</h2><p>Authentication may rely on Firebase/Google, and device functionality may rely on open-source dependencies. Those services and packages are subject to their own terms and licenses. ReMCP does not grant rights to third-party systems that you access from a paired device.</p>
-<h2>Open-source software</h2><p>The ReMCP source distribution includes software under open-source licenses. License notices in the source distribution govern those components independently of these hosted-service Terms.</p>
-<h2>No warranty</h2><p>To the maximum extent permitted by applicable law, the service and software are provided on an “as is” and “as available” basis without warranties of uninterrupted operation, fitness for a particular purpose, or freedom from all defects. Nothing in these Terms limits rights that cannot legally be excluded.</p>
-<h2>Responsibility for losses</h2><p>You are responsible for commands and changes made through devices you authorize. To the maximum extent permitted by applicable law, ReMCP is not responsible for indirect, incidental or consequential losses arising from device changes, lost data, third-party systems or service interruptions. Mandatory consumer or statutory rights remain unaffected.</p>
-<h2>Termination</h2><p>You may stop using the service and revoke your devices at any time. Access may be suspended for security, abuse or legal reasons. Provisions that by their nature should survive termination, including responsibility for prior actions and license obligations, continue to apply.</p>
-<h2>Changes</h2><p>Material changes to these Terms will be published at this URL with a new effective date. Continued use after changes become effective constitutes acceptance where permitted by law.</p>
+    <p><strong>Effective September 16, 2026.</strong> These Terms apply to the hosted ReMCP service at <code>remcp.delio24.com</code>. The open-source software can also be self-hosted under its software licenses.</p>
+
+    <h2>Authorized systems only</h2>
+    <p>You may pair and control only computers and accounts that you own or are authorized to administer. You are responsible for protecting your sign-in account and revoking devices or OAuth grants you no longer trust.</p>
+
+    <h2>Remote actions</h2>
+    <p>ReMCP can read and modify files and can start, interact with or terminate processes. Some commands can affect external systems. Review consequential actions and maintain appropriate backups and operating-system permissions.</p>
+
+    <h2>Acceptable use</h2>
+    <p>Do not use ReMCP to access systems without authorization, steal credentials, distribute malware, evade security controls, interfere with other users, or violate applicable law or third-party rights.</p>
+
+    <h2>Sign-in providers</h2>
+    <p>The hosted service uses Firebase Authentication with Google and GitHub sign-in. Those providers and other infrastructure dependencies are governed by their own terms. ReMCP does not grant rights to third-party systems accessible from a paired computer.</p>
+
+    <h2>Service operation</h2>
+    <p>The hosted service may be updated, rate-limited, suspended or discontinued for security, abuse prevention, maintenance or legal reasons. Uninterrupted availability is not guaranteed. Self-hosted deployments are operated and secured by their administrators.</p>
+
+    <h2>Open-source software</h2>
+    <p>ReMCP and its dependencies include open-source software. Their license notices govern those software components independently of these hosted-service Terms.</p>
+
+    <h2>No warranty</h2>
+    <p>To the maximum extent permitted by applicable law, the service and software are provided “as is” and “as available,” without warranties of uninterrupted operation or fitness for a particular purpose. Rights that cannot legally be excluded remain unaffected.</p>
+
+    <h2>Responsibility for actions</h2>
+    <p>You are responsible for commands and changes made through devices you authorize. To the maximum extent permitted by law, ReMCP is not responsible for indirect or consequential loss arising from device changes, lost data, third-party systems or service interruption.</p>
+
+    <h2>Termination and changes</h2>
+    <p>You may stop using the service and revoke devices at any time. Access may be suspended for security, abuse or legal reasons. Material changes to these Terms will be published at this URL with a new effective date.</p>
   </article>
 </main>
 <footer class="site-footer">
@@ -53,7 +70,7 @@
     <img class="brand-mark" src="/android-chrome-192x192.png" width="30" height="30" alt="" aria-hidden="true">
     <span translate="no">ReMCP</span>
   </div>
-  <nav aria-label="Footer"><a href="/docs">Docs</a><a href="/docs#install">Install</a><a href="/docs#update">Update</a><a href="/security">Security</a><a href="/support">Support</a><a href="/privacy">Privacy</a><a href="/terms">Terms</a></nav>
+  <nav aria-label="Footer"><a href="/docs">Docs</a><a href="/security">Security</a><a href="/support">Support</a><a href="/privacy">Privacy</a><a href="/terms">Terms</a></nav>
   <p>Open-source remote MCP infrastructure.</p>
 </footer>
 </body>

package/skills/remcp-operator/SKILL.md

@@ -33,4 +33,4 @@ Use `start_process` once and then `read_process_output` or `interact_with_proces
 
 ## Out-of-scope requests
 
-Do not use ReMCP to access a computer the user has not paired or is not authorized to control. Do not ask for passwords, MFA codes, private keys, or other credentials through ReMCP tool inputs.
+Do not use ReMCP to access a computer the user has not paired or is not authorized to control. Do not ask for or process passwords, MFA codes, private keys, API keys, payment-card data, protected health information, government identifiers, or other restricted credentials/data through ReMCP tools. If a requested file or command would expose those categories, ask the user to use a safer local workflow instead.

package/src/auth.mjs

@@ -18,6 +18,7 @@ export async function verifyFirebaseToken(token) {
     uid,
     firebaseUid: payload.sub,
     email,
+    emailVerified: payload.email_verified === true,
     name: typeof payload.name === 'string' ? payload.name : '',
   };
 }

package/src/config.mjs

@@ -38,7 +38,7 @@ export const config = Object.freeze({
   refreshTtlSeconds: Number(process.env.REFRESH_TTL_SECONDS || 2592000),
   rpcTimeoutMs: Number(process.env.RPC_TIMEOUT_MS || 120000),
   domainVerificationToken: (process.env.OPENAI_DOMAIN_VERIFICATION_TOKEN || '').trim(),
-  domainVerificationPath: (process.env.OPENAI_DOMAIN_VERIFICATION_PATH || '/.well-known/openai-domain-verification').trim(),
+  domainVerificationPath: (process.env.OPENAI_DOMAIN_VERIFICATION_PATH || '/.well-known/openai-apps-challenge').trim(),
   firebase: {
     apiKey: required('FIREBASE_API_KEY'),
     authDomain: required('FIREBASE_AUTH_DOMAIN'),

package/src/db.mjs

@@ -9,7 +9,7 @@ export const db = new DatabaseSync(join(config.dataDir, 'remcp.sqlite'));
 db.exec(`PRAGMA journal_mode=WAL; PRAGMA foreign_keys=ON; PRAGMA busy_timeout=5000;`);
 db.exec(`
 CREATE TABLE IF NOT EXISTS users (
-  uid TEXT PRIMARY KEY, email TEXT, name TEXT, created_at INTEGER NOT NULL, last_login_at INTEGER NOT NULL
+  uid TEXT PRIMARY KEY, email TEXT, name TEXT, email_verified INTEGER NOT NULL DEFAULT 0, created_at INTEGER NOT NULL, last_login_at INTEGER NOT NULL
 );
 CREATE TABLE IF NOT EXISTS pair_codes (
   code_hash TEXT PRIMARY KEY, uid TEXT NOT NULL REFERENCES users(uid) ON DELETE CASCADE,
@@ -34,12 +34,15 @@ CREATE TABLE IF NOT EXISTS oauth_refresh_tokens (
   scope TEXT NOT NULL, expires_at INTEGER NOT NULL, revoked_at INTEGER
 );
 `);
+try { db.exec('ALTER TABLE users ADD COLUMN email_verified INTEGER NOT NULL DEFAULT 0'); } catch {}
 
-export function upsertUser({ uid, email = '', name = '' }) {
+export const getUser = uid => db.prepare('SELECT * FROM users WHERE uid=?').get(uid);
+
+export function upsertUser({ uid, email = '', name = '', emailVerified = false }) {
   const t = now();
-  db.prepare(`INSERT INTO users(uid,email,name,created_at,last_login_at) VALUES(?,?,?,?,?)
-    ON CONFLICT(uid) DO UPDATE SET email=excluded.email,name=excluded.name,last_login_at=excluded.last_login_at`)
-    .run(uid, email, name, t, t);
+  db.prepare(`INSERT INTO users(uid,email,name,email_verified,created_at,last_login_at) VALUES(?,?,?,?,?,?)
+    ON CONFLICT(uid) DO UPDATE SET email=excluded.email,name=excluded.name,email_verified=excluded.email_verified,last_login_at=excluded.last_login_at`)
+    .run(uid, email, name, emailVerified ? 1 : 0, t, t);
   return db.prepare('SELECT * FROM users WHERE uid=?').get(uid);
 }
 

package/src/mcp.mjs

@@ -57,7 +57,7 @@ function publicTool(tool) {
       readOnlyHint: tool.name === 'start_search' ? false : upstream.readOnlyHint === true,
       destructiveHint: destructive.has(tool.name),
       idempotentHint: upstream.idempotentHint === true,
-      openWorldHint: tool.name === 'read_file' ? false : (openWorld.has(tool.name) || upstream.openWorldHint === true),
+      openWorldHint: openWorld.has(tool.name) || tool.name === 'read_file' || upstream.openWorldHint === true,
     },
   };
 }

package/src/oauth.mjs

@@ -2,9 +2,9 @@ import crypto from 'node:crypto';
 import express from 'express';
 import { rateLimit } from 'express-rate-limit';
 import { config } from './config.mjs';
-import { verifyFirebaseToken, signMcpAccessToken } from './auth.mjs';
-import { createOauthCode, consumeOauthCode, getOauthClient, getRefreshToken, revokeRefreshToken, saveOauthClient, saveRefreshToken, upsertUser } from './db.mjs';
-import { normalizeScope, now, randomId, randomToken, sha256, validRedirectUri } from './util.mjs';
+import { verifyFirebaseToken, signMcpAccessToken, verifyMcpAccessToken } from './auth.mjs';
+import { createOauthCode, consumeOauthCode, getOauthClient, getRefreshToken, getUser, revokeRefreshToken, saveOauthClient, saveRefreshToken, upsertUser } from './db.mjs';
+import { bearer, normalizeScope, now, randomId, randomToken, sha256, validRedirectUri } from './util.mjs';
 
 const CODE_TTL_MS = 5 * 60 * 1000;
 const router = express.Router();
@@ -18,12 +18,13 @@ function metadata() {
     authorization_endpoint: endpoint('/oauth/authorize'),
     token_endpoint: endpoint('/oauth/token'),
     registration_endpoint: endpoint('/oauth/register'),
+    userinfo_endpoint: endpoint('/oauth/userinfo'),
     revocation_endpoint: endpoint('/oauth/revoke'),
     response_types_supported: ['code'],
     grant_types_supported: ['authorization_code', 'refresh_token'],
     token_endpoint_auth_methods_supported: ['none'],
     code_challenge_methods_supported: ['S256'],
-    scopes_supported: ['remcp:control', 'offline_access'],
+    scopes_supported: ['openid', 'email', 'remcp:control', 'offline_access'],
   };
 }
 
@@ -32,7 +33,7 @@ function protectedResource() {
     resource: endpoint('/mcp'),
     authorization_servers: [config.publicUrl],
     bearer_methods_supported: ['header'],
-    scopes_supported: ['remcp:control', 'offline_access'],
+    scopes_supported: ['openid', 'email', 'remcp:control', 'offline_access'],
     resource_documentation: config.publicUrl,
     resource_policy_uri: endpoint('/privacy'),
     resource_tos_uri: endpoint('/terms'),
@@ -136,6 +137,24 @@ router.post('/oauth/token', tokenLimiter, async (req, res) => {
   }
 });
 
+
+router.get('/oauth/userinfo', oauthLimiter, async (req, res) => {
+  noStore(res);
+  try {
+    const token = bearer(req);
+    if (!token) throw new Error('missing_token');
+    const auth = await verifyMcpAccessToken(token);
+    const scopes = new Set(auth.scope.split(/\s+/).filter(Boolean));
+    if (!scopes.has('openid') || !scopes.has('email')) throw new Error('insufficient_scope');
+    const user = getUser(auth.uid);
+    if (!user?.email || user.email_verified !== 1) throw new Error('verified_email_required');
+    res.json({ sub: auth.uid, email: user.email, email_verified: true, ...(user.name ? { name: user.name } : {}) });
+  } catch (error) {
+    res.setHeader('WWW-Authenticate', 'Bearer error="invalid_token"');
+    res.status(401).json({ error: 'invalid_token', error_description: error.message });
+  }
+});
+
 router.post('/oauth/revoke', oauthLimiter, (req, res) => {
   const token = String(req.body?.token || '');
   if (token) revokeRefreshToken(sha256(token));

package/src/util.mjs

@@ -9,7 +9,7 @@ export const bearer = req => {
   return value.startsWith('Bearer ') ? value.slice(7).trim() : '';
 };
 export function normalizeScope(value = '') {
-  const allowed = new Set(['openid', 'offline_access', 'remcp:control']);
+  const allowed = new Set(['openid', 'email', 'offline_access', 'remcp:control']);
   const scopes = String(value).split(/\s+/).filter(Boolean).filter(scope => allowed.has(scope));
   if (!scopes.includes('remcp:control')) scopes.push('remcp:control');
   if (!scopes.includes('offline_access')) scopes.push('offline_access');